1. 27 May, 2013 4 commits
  2. 24 May, 2013 3 commits
  3. 18 May, 2013 1 commit
  4. 15 May, 2013 9 commits
  5. 14 May, 2013 5 commits
  6. 13 May, 2013 4 commits
  7. 09 May, 2013 1 commit
  8. 08 May, 2013 2 commits
    • antirez's avatar
      Version bumped to 2.9.10 · a7486a65
      antirez authored
      a7486a65
    • antirez's avatar
      Revert "use long long instead of size_t make it more safe" · 0ae1b5b0
      antirez authored
      This reverts commit 2c75f2cf.
      
      After further analysis, it is very unlikely that we'll raise the
      string size limit to > 512MB, and at the same time such big strings
      will be used in 32 bit systems.
      
      Better to revert to size_t so that 32 bit processors will not be
      forced to use a 64 bit counter in normal operations, that is currently
      completely useless.
      0ae1b5b0
  9. 07 May, 2013 2 commits
  10. 03 May, 2013 5 commits
  11. 02 May, 2013 3 commits
  12. 30 Apr, 2013 1 commit
    • antirez's avatar
      Sentinel: changes to tilt mode. · e5ef85c4
      antirez authored
      Tilt mode was too aggressive (not processing INFO output), this
      resulted in a few problems:
      
      1) Redirections were not followed when in tilt mode. This opened a
         window to misinform clients about the current master when a Sentinel
         was in tilt mode and a fail over happened during the time it was not
         able to update the state.
      
      2) It was possible for a Sentinel exiting tilt mode to detect a false
         fail over start, if a slave rebooted with a wrong configuration
         about at the same time. This used to happen since in tilt mode we
         lose the information that the runid changed (reboot).
      
         Now instead the Sentinel in tilt mode will still remove the instance
         from the list of slaves if it changes state AND runid at the same
         time.
      
      Both are edge conditions but the changes should overall improve the
      reliability of Sentinel.
      e5ef85c4