1. 05 Nov, 2013 4 commits
  2. 31 Oct, 2013 2 commits
  3. 28 Oct, 2013 8 commits
  4. 25 Oct, 2013 14 commits
  5. 11 Oct, 2013 2 commits
  6. 09 Oct, 2013 4 commits
  7. 08 Oct, 2013 1 commit
    • antirez's avatar
      Cluster: masters don't vote for a slave with stale config. · ae2763f5
      antirez authored
      When a slave requests our vote, the configEpoch he claims for its master
      and the set of served slots must be greater or equal to the configEpoch
      of the nodes serving these slots in the current configuraiton of the
      master granting its vote.
      
      In other terms, masters don't vote for slaves having a stale
      configuration for the slots they want to serve.
      ae2763f5
  8. 07 Oct, 2013 3 commits
  9. 04 Oct, 2013 2 commits
    • antirez's avatar
      Replication: install the write handler when reusing a cached master. · 0150c70b
      antirez authored
      Sometimes when we resurrect a cached master after a successful partial
      resynchronization attempt, there is pending data in the output buffers
      of the client structure representing the master (likely REPLCONF ACK
      commands).
      
      If we don't reinstall the write handler, it will never be installed
      again by addReply*() family functions as they'll assume that if there is
      already data pending, the write handler is already installed.
      
      This bug caused some slaves after a successful partial sync to never
      send REPLCONF ACK, and continuously being detected as timing out by the
      master, with a disconnection / reconnection loop.
      0150c70b
    • antirez's avatar
      Replication: install the write handler when reusing a cached master. · 1461422c
      antirez authored
      Sometimes when we resurrect a cached master after a successful partial
      resynchronization attempt, there is pending data in the output buffers
      of the client structure representing the master (likely REPLCONF ACK
      commands).
      
      If we don't reinstall the write handler, it will never be installed
      again by addReply*() family functions as they'll assume that if there is
      already data pending, the write handler is already installed.
      
      This bug caused some slaves after a successful partial sync to never
      send REPLCONF ACK, and continuously being detected as timing out by the
      master, with a disconnection / reconnection loop.
      1461422c