'Failover' Tag

  • orchestrator/raft: Pre-Release 3.0

    August 3, 2017

    orchestrator 3.0 Pre-Release is now available. Most notable are Raft consensus, SQLite backend support, orchestrator-client no-binary-required client script. TL;DR You may now set up high availability for orchestrator via raft consensus, without need to set up high availability for orchestrator's backend MySQL servers (such as Galera/InnoDB Cluster). In fact, you can run a orchestrator/raft setup […]

  • State of automated recovery via Pseudo-GTID & Orchestrator @ Booking.com

    November 20, 2015

    This post sums up some of my work on MySQL resilience and high availability at Booking.com by presenting the current state of automated master and intermediate master recoveries via Pseudo-GTID & Orchestrator. Booking.com uses many different MySQL topologies, of varying vendors, configurations and workloads: Oracle MySQL, MariaDB, statement based replication, row based replication, hybrid, OLTP, […]

  • Orchestrator & Pseudo-GTID for binlog reader failover

    November 19, 2015

    One of our internal apps at Booking.com audits changes to our tables on various clusters. We used to use tungsten replicator, but haveĀ since migrated onto our own solution. We have a binlog reader (uses open-replicator) running on a slave. It expects Row Based Replication, hence our slave runs with log-slave-updates, binlog-format='ROW', to translate from the […]

  • Thoughts on MaxScale automated failover (and Orchestrator)

    November 18, 2015

    Having attended a talk (as part of the MariaDB Developer Meeting in Amsterdam) about recent developments of MaxScale in executing automated failovers, here are some (late) observations of mine. I will begin by noting that the project is stated to be pre-production, and so of course none of the below are complaints, but rather food […]

  • What makes a MySQL server failure/recovery case?

    July 25, 2015

    Or: How do you reach the conclusion your MySQL master/intermediate-master is dead and must be recovered? This is an attempt at makingĀ a holistic diagnosis of our replication topologies. The aim is to cover obvious and not-so-obvious crash scenarios, and to be able to act accordingly and heal the topology. At Booking.com we are dealing with […]

 
Powered by Wordpress and MySQL. Theme by openark.org