'Replication' Tag

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

  • orchestrator 1.1.18: new features, support for orchestrator-agent

    October 13, 2014

    Outbrain's orchestrator 1.1.18 is released: Support for orchestrator-agent (see announcement): agent pages, support for agent actions, initiation of seeds (provisioning of new/corrupted servers), auditing of seeds. Clusters dashboard Support for long query auditing SSL Proxy authentication (e.g. apache2 serving as reverse-proxy with LDAP) User control Better slave moving rules. Quick links: Get orchestrator 1.1.18 Read […]

  • Announcing orchestrator-agent

    October 13, 2014

    orchestrator-agent is a side-kick, complementary project of orchestrator, implementing a daemon service on one's MySQL hosts which communicates with and accepts commands from orchestrator, built with the original purpose of providing an automated solution for provisioning new or corrupted slaves. It was built by Outbrain, with Outbrain's specific use case in mind. While we release […]

  • Orchestrator 1.0.5: refactoring masters, multi-master replication

    August 6, 2014

    Outbrain's orchestrator Version 1.0.5 is released. Quick links: Orchestrator Manual, FAQ, Downloads Orchestrator now supports refactoring of masters via master-master topologies. It now allows promoting slaves as co-masters and detachment of instances from a co-master topology, effectively allowing for replacing an active master. Like this Drag a master: Onto one of its slaves:

  • Orchestrator 1.0.4 released

    July 29, 2014

    Outbrain's orchestrator Version 1.0.4 is released. Quick links: Orchestrator Manual, FAQ, Downloads What's new? Co-masters orchestrator now does a much better visualization of Master-Master replication:

  • Introducing Orchestrator: manage and visualize your MySQL replication topologies and get home for dinner

    June 9, 2014

    I'm happy to announce the availability of Outbrain's Orchestrator: MySQL replication management & visualization tool. Orchestrator reads your replication topologies (give it one server - be it master or slave - in each topology, and it will reveal the rest). It keeps a state of this topology. It can continuously poll your servers to get […]

  • Using deep nested replication topologies

    June 2, 2014

    If you're running more than a few slaves in a replication topology, you might choose to use deeply nested replication: slaves replicating from other slaves at 2, 3 or even 4 levels. There are pros and cons to such topologies, discussed below. A simple, small deep nested topology is depicted below (it is also a […]

  • From Percona Server to MySQL and back to Percona Server: beware of crash safe replication info

    May 27, 2014

    We're migrating some of our "vanilla" MySQL 5.5 servers to Percona Server 5.5. One of the major incentives is the crash-safe replication feature, allowing slaves to die (power failure) and resume replication without losing position in relay logs. Whether or not we will migrate all our servers depends on further benchmarking; so far we've noticed […]

 
Powered by Wordpress and MySQL. Theme by openark.org