The Mighty Buzzard writes:
Yeah, so, failure to babysit the db node that was scheduled for a reboot on the 5th resulted in a bit of database FUBAR that left us temporarily losing everything from then to now. Fortunately we had a backup less than six hours old, restored from it, and appear to be copacetic now. Except for the missing five hours and change.
I'd usually make some sort of dumb joke here but it was already four hours past my bedtime when I found out about the problem. My brain is no work good anymore. Fill in whatever dad joke or snark about getting a do-over for a change strikes your fancy.
(Score: 2) by The Mighty Buzzard on Monday August 10 2020, @04:56AM
Two nodes is plenty for our purposes. Our network load vs. the bandwidth between our boxes makes replication essentially instant unless you have to completely restore a node, so mostly what we need is for the web frontends to not have to give a shit what db server they're dealing with in the event that one of them crashes. If we were looking to fail to read-only, we'd have stuck with master/slave. We consider read-only to be failure though.
My rights don't end where your fear begins.