Stories
Slash Boxes
Comments

SoylentNews is people

Meta: Sigh

posted by on Sunday August 09 2020, @05:51AM   Printer-friendly
from the SNAFU dept.

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.

 
This discussion has been archived. No new comments can be posted.
Meta: Sigh | Log In/Create an Account | Top | 114 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Tuesday August 11 2020, @01:14AM

    by Anonymous Coward on Tuesday August 11 2020, @01:14AM (#1034657)

    I meant primary and not arbitrator. It should definitely be the arbitrator too. But it is recommended practice to have the primary management node not be a data node as well. It helps with solving problems with quorum, split brain, and other issues, while also allowing centralized service management from a single node.