1. 06 Dec, 2013 3 commits
    • antirez's avatar
      Sentinel: fix reported role info sampling. · c590549e
      antirez authored
      The way the role change was recoded was not sane and too much
      convoluted, causing the role information to be not always updated.
      
      This commit fixes issue #1445.
      c590549e
    • antirez's avatar
      Sentinel: fix reported role fields when master is reset. · 2b414a4b
      antirez authored
      When there is a master address switch, the reported role must be set to
      master so that we have a chance to re-sample the INFO output to check if
      the new address is reporting the right role.
      
      Otherwise if the role was wrong, it will be sensed as wrong even after
      the address switch, and for enough time according to the role change
      time, for Sentinel consider the master SDOWN.
      
      This fixes isue #1446, that describes the effects of this bug in
      practice.
      2b414a4b
    • antirez's avatar
      Fixed typo in redis.conf. · 8534a290
      antirez authored
      8534a290
  2. 05 Dec, 2013 9 commits
  3. 04 Dec, 2013 1 commit
  4. 03 Dec, 2013 4 commits
  5. 02 Dec, 2013 3 commits
    • antirez's avatar
      Sentinel: don't write HZ when flushing config. · f80cf736
      antirez authored
      See issue #1419.
      f80cf736
    • antirez's avatar
      Sentinel: better time desynchronization. · dffebbc9
      antirez authored
      Sentinels are now desynchronized in a better way changing the time
      handler frequency between 10 and 20 HZ. This way on average a
      desynchronization of 25 milliesconds is produced that should be larger
      enough compared to network latency, avoiding most split-brain condition
      during the vote.
      
      Now that the clocks are desynchronized, to have larger random delays when
      performing operations can be easily achieved in the following way.
      Take as example the function that starts the failover, that is
      called with a frequency between 10 and 20 HZ and will start the
      failover every time there are the conditions. By just adding as an
      additional condition something like rand()%4 == 0, we can amplify the
      desynchronization between Sentinel instances easily.
      
      See issue #1419.
      dffebbc9
    • antirez's avatar
      Cluster: nodes re-addition blacklist API. · 6fa42b75
      antirez authored
      6fa42b75
  6. 29 Nov, 2013 2 commits
  7. 28 Nov, 2013 3 commits
  8. 26 Nov, 2013 2 commits
  9. 25 Nov, 2013 3 commits
  10. 21 Nov, 2013 9 commits
  11. 20 Nov, 2013 1 commit