Planet MySQL Planet MySQL: Meta Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 10 of 10

Displaying posts with tag: orchestrator (reset)

Refactoring replication topologies with Pseudo GTID: a visual tour
+0 Vote Up -0Vote Down

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 via web API (in fact, the drag-and-drop invoke the web API) as well as via command line. I'm mentioning this as this is the grounds for failover automation planned for the future.

Scenario 1: the master unexpectedly dies

The

  [Read more...]
Orchestrator 1.2.1 BETA: Pseudo GTID support, reconnect slaves even after master failure
+0 Vote Up -0Vote Down

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
  •   [Read more...]
    Refactoring replication topology with Pseudo GTID
    +0 Vote Up -0Vote Down

    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, and its three slaves are all hanging, not necessarily at same binary log file/position (network broke down while some slaves managed to salvage more entries into their relay logs than others)

      [Read more...]
    Pseudo GTID, Row Based Replication
    +0 Vote Up -0Vote Down

    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  end_log_pos 1074  Table_map: `test`.`pseudo_gtid` mapped to number 33
    #141020 12:36:21 server id 1  end_log_pos 1196  Update_rows: table id 33 flags: STMT_END_F
    
    BINLOG '
    lddEVBMBAAAANgAAADIEAAAAACEAAAAAAAEABHRlc3QAC3BzZXVkb19ndGlkAAMDBw8CQAAE
    lddEVBgBAAAAegAAAKwEAAAAACEAAAAAAAEAA///+AEAAACL10RUJDg2ZmRhMDk1LTU4M2MtMTFl
    NC05NzYyLTNjOTcwZWEzMWVhOPgBAAAAlddEVCQ4Y2YzOWMyYy01ODNjLTExZTQtOTc2Mi0zYzk3
    MGVhMzFlYTg=
    '/*!*/;
    

    Where's our unique value? Encoded within

      [Read more...]
    Pseudo GTID
    +0 Vote Up -0Vote Down

    Pseudo GTID is a method to implement a GTID-like solution where slaves are easily connected to one another. This blog post and the following ones will describe work in progress (some 80% completed), where simulation of GTID makes for a good enough basis for refactoring replication topologies. I'm coding this in orchestrator, which already provides a substantial infrastructure support for this.

    The final goal: orchestrator will allow you to move a slave below another, using only the data available by those two slaves. The usage is obvious:

    • Easy master failover (master dead? Orchestrator will choose the most advanced slave to promote and make it master of its siblings)
    • Slave promotion in complex topologies (with
      [Read more...]
    orchestrator 1.1.18: new features, support for orchestrator-agent
    +0 Vote Up -0Vote Down

    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:

      [Read more...]
    Announcing orchestrator-agent
    +0 Vote Up -0Vote Down

    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 it as open source, only a small part of its functionality will appeal to the public (this is why it's not strictly part of the orchestrator project, which is a general purpose, wide-audience solution). Nevertheless, it is a simple implementation of a daemon, such that can be easily extended by

      [Read more...]
    Orchestrator 1.0.5: refactoring masters, multi-master replication
    +0 Vote Up -0Vote Down

    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:

      [Read more...]
    Orchestrator 1.0.4 released
    +1 Vote Up -0Vote Down

    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:

      [Read more...]
    Introducing Orchestrator: manage and visualize your MySQL replication topologies and get home for dinner
    +1 Vote Up -0Vote Down

    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 an up to date topology map.
    • It visualizes the topology in a clear and slick D3 tree.
    • It allows you
      [Read more...]
    Showing entries 1 to 10 of 10

    Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

    Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.