The other thing to watch out for is if you’re splitting state between volumes, but i think you’ve already ruled that out.
The other thing to watch out for is if you’re splitting state between volumes, but i think you’ve already ruled that out.
I’d be cautious about the “kill -9” reasoning. It isn’t necessarily equivalent to yanking power.
Contents of application memory lost, yes. Contents of unflushed OS buffers, no. Your db will be fsyncing (or moral equivalent thereof) if it’s worth the name.
This is an aside; backing up from a volume snapshot is half a reasonable idea. (The other half is ensuring that you can restore from the backup, regularly, automatically, and the third half is ensuring that your automated validation can be relied on.)
…unless it’s running software that uses signed 32-bit timestamps, or stores data using that format.
The point about the “millennium bug” was that it was a category of problems that required (hundreds of) thousands of fixes. It didn’t matter if your OS was immune, because the OS isn’t where the value is.
Dare I ask what the adjective “hella” means in this context?
Came here to mention laser cooling; glad someone else got there first.
Figure eight on a bight.