An error occurred fetching the project authors.
  1. 02 Jun, 2010 1 commit
  2. 01 Jun, 2010 1 commit
  3. 10 Mar, 2010 1 commit
  4. 23 Feb, 2010 1 commit
    • He Zhenxing's avatar
      Bug#49557 "semisync" plugin test fails on Windows · 522311e0
      He Zhenxing authored
      The problem was because the gettimeofday function was incorrect
      implemented for Windows, and so the semisync master did not wait
      for slave reply properly on Windows.
      
      Fixed by removing the gettimeofday function for Windows, and using
      set_timespec function to get current time for all platforms.
      522311e0
  5. 30 Jan, 2010 1 commit
    • 's avatar
      BUG#50157 Assertion !active_tranxs_->is_tranx_end_pos(..) in ReplSemiSyncMaster::commitTrx · 85589577
      authored
      The root cause of the crash is that a TranxNode is freed before it is used.
      A TranxNode is allocated and inserted into the active list each time 
      a log event is written and flushed into the binlog file. 
      The memory for TranxNode is allocated with thd_alloc and will be freed 
      at the end of the statement. The after_commit/after_rollback callback
      was supposed to be called before the end of each statement and remove the node from
      the active list. However this assumption is not correct in all cases(e.g. call 
      'CREATE TEMPORARY TABLE myisam_t SELECT * FROM innodb_t' in a transaction
       and delete all temporary tables automatically when a session closed), 
      and can cause the memory allocated for TranxNode be freed
      before it was removed from the active list. So The TranxNode pointer in the active
      list would become a wild pointer and cause the crash.
      
      After this patch, We have a class called a TranxNodeAllocate which manages the memory
      for allocating and freeing TranxNode. It uses my_malloc to allocate memory.
      85589577
  6. 04 Dec, 2009 2 commits
    • He Zhenxing's avatar
      Post fix for previous patch of Bug#49020 · eaf517bc
      He Zhenxing authored
      Added back n_frees, use 'clear' instead of 'free' since memory is
      not freed here.
      eaf517bc
    • He Zhenxing's avatar
      Bug#49020 Semi-sync master crashed with free_pool == NULL, assertion `free_pool_' · 16ec25c0
      He Zhenxing authored
      Before this patch, semisync assumed transactions running in parallel
      can not be larger than max_connections, but this is not true when
      the event scheduler is executing events, and cause semisync run out
      of preallocated transaction nodes.
      
      Fix the problem by allocating transaction nodes dynamically.
      
      This patch also fixed a possible deadlock when running UNINSTALL
      PLUGIN rpl_semi_sync_master and updating in parallel. Fixed by
      releasing the internal Delegate lock before unlock the plugins.
      16ec25c0
  7. 23 Oct, 2009 1 commit
  8. 12 Oct, 2009 3 commits
    • He Zhenxing's avatar
      Backport BUG#47298 Semisync: always wait until timeout if no semi-sync slave available · b92ec529
      He Zhenxing authored
      Add an option to control whether the master should keep waiting
      until timeout when it detected that there is no semi-sync slave
      available.
      
      The bool option 'rpl_semi_sync_master_wait_no_slave' is 1 by
      defalt, and will keep waiting until timeout. When set to 0, the
      master will switch to asynchronous replication immediately when
      no semi-sync slave is available.
      b92ec529
    • He Zhenxing's avatar
      BUG#45674 FLUSH STATUS does not reset semisynchronous counters · 64fc766c
      He Zhenxing authored
      Semi-sync status were not reset by FLUSH STATUS, this was because
      all semi-sync status variables are defined as SHOW_FUNC and FLUSH
      STATUS could only reset SHOW_LONG type variables.
      
      This problem is fixed by change all status variables that should
      be reset by FLUSH STATUS from SHOW_FUNC to SHOW_LONG.
      
      After the fix, the following status variables will be reset by
      FLUSH STATUS:
        Rpl_semi_sync_master_yes_tx
        Rpl_semi_sync_master_no_tx
      
      Note: normally, FLUSH STATUS itself will be written into binlog
      and be replicated, so after FLUSH STATS, one of
        Rpl_semi_sync_master_yes_tx
        Rpl_semi_sync_master_no_tx
      can be 1 dependent on the semi-sync status. So it's recommended
      to use FLUSH NO_WRITE_TO_BINLOG STATUS to avoid this.
      64fc766c
    • 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
  9. 03 Oct, 2009 1 commit
  10. 26 Sep, 2009 1 commit