'Pseudo GTID' Tag

  • 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 […]

  • Orchestrator visual cheatsheet, TL;DR the "smart" way

    September 2, 2015

    Orchestrator is really growing. And the amount of users (DBAs, sys admins) using it is growing. Which gives me a lot of immediate feedback in the form of "Look, there's just too many options to move slaves around! Which ones should we use?" TL;DR look at the two visualized commands below They are enough The "smart" commands to […]

  • Orchestrator 1.4.340: GTID, binlog servers, Smart Mode, failovers and lots of goodies

    September 1, 2015

    Orchestrator 1.4.340 is released. Not quite competing with the MySQL latest changelog, and as I haven't blogged about orchestrator featureset in a while, this is a quick listing of orchestrator features available since my last publication: Supports GTID (Oracle & MariaDB) GTID still not being used in automated recovery -- in progress. enable-gtid, disable-gtid, skip-query for GTID commands […]

  • Pseudo GTID, ASCENDING

    July 29, 2015

    Pseudo GTID is a technique where we inject Globally Unique entries into MySQL, gaining GTID abilities without using GTID. It is supported by orchestrator and described in more detail here, here and here. Quick recap: we can join two slaves to replicate from one another even if they never were in parent-child relationship, based on our […]

  • Speaking at Percona Live: Pseudo GTID and Easy Replication Topology Management

    March 31, 2015

    In two weeks time I will be presenting Pseudo GTID and Easy Replication Topology Management at Percona Live. From the time I submitted the proposal a LOT has been developed, experimented, deployed and used with both Pseudo GTID and with orchestrator. In my talk I will: Suggest that you skip the "to GTID or not to GTID" question […]

  • Speaking at FOSDEM: Pseudo GTID and easy replication management

    January 29, 2015

    This coming Sunday I'll be presenting Pseudo GTID and easy replication management at FOSDEM, Brussels. There's been a lot of development on Pseudo GTID these last few weeks. In this talk I'll show you how you can use Pseudo GTID instead of "normal" GTID to easily repoint your slaves, recover from intermediate master failure, promote slaves to […]

  • Semi-automatic slave/master promotion via Pseudo GTID

    November 10, 2014

    Orchestrator release 1.2.7-beta now supports semi-automatic slave promotion to master upon master death, via Pseudo GTID. When the master is dead, orchestrator automatically picks the most up-to-date slaves and marks them as "Master candidates". It allows a /api/make-master call on such a slave (S), in which case it uses Pseudo GTID to enslave its siblings, […]

  • Refactoring replication topologies with Pseudo GTID: a visual tour

    October 27, 2014

    Orchestrator 1.2.1-beta supports Pseudo GTID (read announcement): a means to refactor the replication topology and connect slaves even without direct relationship; even across failed servers. This post illustrates two such scenarios and shows the visual way of mathcing/re-synching slaves. Of course, orchestrator is not just a GUI tool; anything done with drag-and-drop is also done […]

  • Orchestrator 1.2.1 BETA: Pseudo GTID support, reconnect slaves even after master failure

    October 27, 2014

    orchestrator 1.2.1 BETA is released. This version supports Pseudo GTID, and provides one with powerful refactoring of one's replication topologies, even across failed instances. Depicted: moving a slave up the topology even though its local master is inaccessible Enabling Pseudo-GTID You will need to: Inject a periodic unique entry onto your binary logs Configure orchestrator […]

 
Powered by Wordpress and MySQL. Theme by openark.org