3 ms·
I wonder what is this database, and why it is hard to fall-over automatically.
by ferguess_k 1mo ago
I wonder what is this database, and why it is hard to fall-over automatically.
- inigyou 1mo agoRDBMS replication and failover is way more difficult and manual than anyone would like. You can't just set up two postgres, tell them they're clustered and have it basically work; at a minimum you have to design the client to somehow know which one is currently the master, or use some sort of proxy (which becomes its own SPOF). RDBMS integrity basically requires that one master server is responsible for the whole data set and other servers may replicate from it. And it usually doesn't wait for a quorum of replicas, just for one, because the design is to recover from a hardware failure, not a network partition, although that could be fixed at the cost of increased latency.
- ferguess_k 1mo agoThanks! I didn't get the chance to manage RDBMs but that's good to know.
- winrid 1mo agoMongo will auto failover if you have 3+ replicas. Primary knowledge is abstracted into the driver or query router level depending on setup.
- inigyou 1mo agoWe all know that /dev/null is web scale. This can be implemented in front of any RDBMS as a separate layer. Traditionally they weren't designed for quorum-sensing since it hadn't been invented yet. I'd be surprised if something like pgbouncer couldn't do it.
- winrid 1mo agoYou can do that. It's called vitess/citus ^_^
- croemer 1mo agoPossibly vitess from the latest update: > primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
- ferguess_k 1mo agoThanks!