4 ms·
I’m not super versed in MySQL failover, but am I correct to conclude the Orchestrator and RAFT also did them in? And isn’t that architectural components right t
by tnolet 8y ago
I’m not super versed in MySQL failover, but am I correct to conclude the Orchestrator and RAFT also did them in? And isn’t that architectural components right to existence to exactly prohibit such a situation from happening? Genuine question.
- jrochkind1 8y agoDoes this text from the thing you are replying to answer your question? > Adjust the configuration of Orchestrator to prevent the promotion of database primaries across regional boundaries. Orchestrator’s actions behaved as configured, despite our application tier being unable to support this topology change. Leader-election within a region is generally safe, but the sudden introduction of cross-country latency was a major contributing factor during this incident. This was emergent behavior of the system given that we hadn’t previously seen an internal network partition of this magnitude. (Does anyone even read the things anymore?)
- tnolet 8y agoPlease assume best intentions. I read the whole thing. Top to bottom. Just trying to learn.
- jrochkind1 8y agoyou're right, sorry.
- sitharus 8y agoOrchestrator and RAFT did not help them, but mostly it was their configuration. The setup allowed an automatic failover to the west cost data centre, so when the connectivity failed the tools did their job and voted in the west coast. The solution applied is to prohibit cross-country failover in Orchestrator, but allow it to continue doing failover within regions.