3 ms·
Great post! Do you use semi-synchronous or asynchronous replication? If you use asynchronous replication, when a server crashes and this triggers the automated
by ngrilly 9y ago
Great post! Do you use semi-synchronous or asynchronous replication? If you use asynchronous replication, when a server crashes and this triggers the automated failover, do you lose the last transactions?
- ngrilly 9y agoIt looks like the answer to my question is here: https://githubengineering.com/orchestrator-github/ https://githubengineering.com/orchestrator-github/
- sciurus 9y agoThe author of Orchestrator also goes into questions like that at http://code.openark.org/blog/mysql/mysql-high-availability-tools-followup-the-missing-piece-orchestrator http://code.openark.org/blog/mysql/mysql-high-availability-t... Tangentially, in that blog post I was impressed by the list of companies running orchestrator. > orchestrator is actively maintained by GitHub. It manages automated failovers at GitHub. It manages automated failovers at Booking.com, one of the largest MySQL setups on this planet. It manages automated failovers as part of Vitess. These are some names I’m free to disclose, and browsing the issues shows a few more users running failovers in production. Otherwise, it is used for topology management and visualization in a large number of companies such as Square, Etsy, Sendgrid, Godaddy and more.
- ngrilly 9y agoThanks for the link: it's a fantastic read!