How so?
-
-
This Tweet is unavailable.
-
Hmm, I don't think any situation that resulted in cross-region MySQL traffic would have. Orchestrator worked as configured, but the resulting MySQL topology couldn't cope! (We have cross-region hijinx at PD, it's hard to get right!)
End of conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
are you sure it was a raft leader promotion problem and not a mysql primary promotion problem? (I thought Orchestrator _worked_ but made unsustainable decisions.)
i.e. i don’t think you were wrong?