1. 12 Oct, 2009 2 commits
    • He Zhenxing's avatar
      Backport Bug#45852 Semisynch: Last_IO_Error: Fatal error: Failed to run 'after_queue_event' hook · 7d3d0fc3
      He Zhenxing authored
      Errors when send reply to master should never cause the IO thread
      to stop, because master can fall back to async replication if it
      does not get reply from slave.
      
      The problem is fixed by deliberately ignoring the return value of
      slaveReply.
      7d3d0fc3
    • He Zhenxing's avatar
      Backport BUG#45848 Semisynchronous replication internals are visible in SHOW PROCESSLIST and logs · 55842061
      He Zhenxing authored
      Semi-sync uses an extra connection from slave to master to send
      replies, this is a normal client connection, and used a normal
      SET query to set the reply information on master, which is visible
      to user and may cause some confusion and complaining.
      
      This problem is fixed by using the method of sending reply by
      using the same connection that is used by master dump thread to
      send binlog to slave. Since now the semi-sync plugins are integrated
      with the server code, it is not a problem to use the internal net
      interfaces to do this.
      
      The master dump thread will mark the event requires a reply and
      wait for the reply when the event just sent is the last event
      of a transaction and semi-sync status is ON; And the slave will
      send a reply to master when it received such an event that requires
      a reply.
      55842061
  2. 03 Oct, 2009 1 commit
  3. 02 Oct, 2009 2 commits
  4. 30 Sep, 2009 2 commits
  5. 26 Sep, 2009 1 commit
  6. 21 Sep, 2009 1 commit
  7. 04 Sep, 2009 1 commit
  8. 03 Sep, 2009 6 commits
  9. 02 Sep, 2009 17 commits
  10. 01 Sep, 2009 7 commits