An error occurred fetching the project authors.
  1. 28 May, 2013 1 commit
    • unknown's avatar
      MDEV-4478: Implement GTID "strict mode" · ee2b7db3
      unknown authored
      When @@GLOBAL.gtid_strict_mode=1, then certain operations result
      in error that would otherwise result in out-of-order binlog files
      between servers.
      
      GTID sequence numbers are now allocated independently per domain;
      this results in less/no holes in GTID sequences, increasing the
      likelyhood that diverging binlogs will be caught by the slave when
      GTID strict mode is enabled.
      ee2b7db3
  2. 22 May, 2013 1 commit
    • unknown's avatar
      MDEV-26: Global transaction ID. · 1cd6eb5f
      unknown authored
      Change of user interface to be more logical and more in line with expectations
      to work similar to old-style replication.
      
      User can now explicitly choose in CHANGE MASTER whether binlog position is
      taken into account (master_gtid_pos=current_pos) or not (master_gtid_pos=
      slave_pos) when slave connects to master.
      
      @@gtid_pos is replaced by three separate variables @@gtid_slave_pos (can
      be set by user, replicated GTIDs only), @@gtid_binlog_pos (read only), and
      @@gtid_current_pos (a combination of the two, most recent GTID within each
      domain). mysql.rpl_slave_state is renamed to mysql.gtid_slave_pos to match.
      
      This fixes MDEV-4474.
      1cd6eb5f
  3. 05 Apr, 2013 1 commit
    • unknown's avatar
      MDEV-26: Global transaction ID. · b7363eb4
      unknown authored
      Replace CHANGE MASTER TO ... master_gtid_pos='xxx' with a new system
      variable @@global.gtid_pos.
      
      This is more logical; @@gtid_pos is global, not per-master, and it is not
      affected by RESET SLAVE.
      
      Also rename master_gtid_pos=AUTO to master_use_gtid=1, which again is more
      logical.
      b7363eb4
  4. 02 Apr, 2013 1 commit
    • unknown's avatar
      MDEV-26: Global transaction ID · bdf6367d
      unknown authored
      More fixes for test failures in Buildbot:
      
       - Do not run crashing test in Valgrind.
      
       - FLUSH TABLES did not work to avoid errors about not closed tables when
         crashing server. Suppress the messages instead.
      
       - Rewrite multi-source test case to only start one pair of slave threads at a
         time, to work-around the bug MDEV-4352.
      bdf6367d
  5. 29 Mar, 2013 1 commit
  6. 28 Mar, 2013 1 commit
    • unknown's avatar
      MDEV-26: Global transaction ID. · 5aaf73fc
      unknown authored
      Add tests crashing the slave in the middle of replication and checking that
      replication picks-up again on restart in a crash-safe way.
      
      Fix silly code that causes crash by inserting uninitialised data into a hash.
      5aaf73fc
  7. 27 Mar, 2013 1 commit
    • unknown's avatar
      MDEV-26: Global transaction ID. · b0389850
      unknown authored
      Test crashing the master, check that it recovers the binlog state.
      
      Fix one bug introduced by previous commit (crash-recoved binlog state was
      overwritten by loading stale binlog state file).
      
      Fix Windows build error.
      b0389850
  8. 26 Mar, 2013 1 commit
    • unknown's avatar
      MDEV-26: Global transaction ID · d9f975d0
      unknown authored
      Adjust full test suite to work with GTID.
      
      Huge patch, mainly due to having to update .result file for all SHOW BINLOG
      EVENTS and mysqlbinlog outputs, where the new GTID events pop up.
      
      Everything was painstakingly checked to be still correct and valid .result
      file updates.
      d9f975d0
  9. 21 Mar, 2013 1 commit
    • unknown's avatar
      MDEV-26: Global transaction ID. · 9bb989a9
      unknown authored
      Fix MDEV-4275 - I/O thread restart duplicates events in the relay log.
      The first time we connect to master after CHANGE MASTER or restart, we connect
      from the GTID position. But then subsequent reconnects or IO thread restarts
      reconnect with the old-style file/offset binlog pos from where it left off at
      last disconnect. This is necessary to avoid duplicate events in the relay
      logs, as there is nothing that synchronises the SQL thread update of GTID
      state (multiple threads in case of multi-source) with IO thread reconnects.
      
      Test cases.
      
      Some small cleanups and fixes.
      9bb989a9