'Replication' Tag

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

  • Reading RBR binary logs with pt-query-digest

    January 26, 2015

    For purposes of auditing anything that goes on our servers we're looking to parse the binary logs of all servers (masters), as with "Anemomaster". With Row Based Replication this is problematic since pt-query-digest does not support parsing RBR binary logs (true for 2.2.12, latest at this time). I've written a simple script that translates RBR […]

  • Orchestrator 1.2.9 GA released

    December 18, 2014

    Orchestrator 1.2.9 GA has been released. Noteworthy: Added "ReadOnly" (true/false) configuration param. You can have orchestrator completely read-only Added "AuthenticationMethod": "multi": works like BasicAuth (your normal HTTP user+password) only it also accepts the special user called "readonly", which, surprise, can only view and not modify Centralized/serialized most backend database writes (with hundreds/thousands monitored servers it […]

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

  • Refactoring replication topology with Pseudo GTID

    October 23, 2014

    This post describes in detail the method of using Pseudo GTID to achieve unplanned replication topology changes, i.e. connecting two arbitrary slaves, or recovering from a master failure even as all its slaves are hanging in different positions. Please read Pseudo GTID and Pseudo GTID, RBR as introduction. Consider the following case: the master dies unexpectedly, […]

  • Pseudo GTID, Row Based Replication

    October 23, 2014

    This post continues Pseudo GTID, in a series of posts describing an alternative to using MySQL GTIDs. The solution offered in the last post does not work too well for row based replication. The binary log entries for the INSERT statement look like this: # at 1020 # at 1074 #141020 12:36:21 server id 1  […]

  • Making UUID() and RAND() replication safe

    October 20, 2014

    MySQL's UUID() and RAND() functions both provide with (pseudo) indeterministic result. UUID()'s result is moreover bound to the host on which it executes. For this reason, both are unsafe to replicate with STATEMENT binlog format. As an example, consider: master> create table test.uuid_test (id int, u varchar(64)); master> insert into test.uuid_test values (1, UUID()); Query […]

 
Powered by Wordpress and MySQL. Theme by openark.org