1. 13 Nov, 2013 12 commits
  2. 12 Nov, 2013 10 commits
  3. 11 Nov, 2013 4 commits
    • antirez's avatar
      Sentinel: leadership handling changes WIP. · 8c1bf9a2
      antirez authored
      Changes to leadership handling.
      
      Now the leader gets selected by every Sentinel, for a specified epoch,
      when the SENTINEL is-master-down-by-addr is sent.
      
      This command now includes the runid and the currentEpoch of the instance
      seeking for a vote. The Sentinel only votes a single time in a given
      epoch.
      
      Still a work in progress, does not even compile at this stage.
      8c1bf9a2
    • antirez's avatar
      Sentinel: handle Hello messages received via slaves correctly. · 0bac36d0
      antirez authored
      Even when messages are received via the slave, we should perform
      operations (like adding a new Sentinel) in the context of the master.
      0bac36d0
    • antirez's avatar
      9e1b27d4
    • antirez's avatar
      Sentinel: epoch introduced. · b93b0adc
      antirez authored
      Sentinel state now includes the idea of current epoch and config epoch.
      In the Hello message, that is now published both on masters and slaves,
      a Sentinel no longer just advertises itself but also broadcasts its
      current view of the configuration: the master name / ip / port and its
      current epoch.
      
      Sentinels receiving such information switch to the new master if the
      configuration epoch received is newer and the ip / port of the master
      are indeed different compared to the previos ones.
      b93b0adc
  4. 06 Nov, 2013 3 commits
  5. 26 Sep, 2013 1 commit
  6. 24 Jul, 2013 1 commit
    • antirez's avatar
      sdsrange() does not need to return a value. · 6ea8e094
      antirez authored
      Actaully the string is modified in-place and a reallocation is never
      needed, so there is no need to return the new sds string pointer as
      return value of the function, that is now just "void".
      6ea8e094
  7. 11 Jul, 2013 2 commits
  8. 10 Jul, 2013 1 commit
  9. 09 Jul, 2013 1 commit
  10. 08 Jul, 2013 2 commits
  11. 20 Jun, 2013 1 commit
    • antirez's avatar
      Sentinel: parse new INFO replication output correctly. · 4c0f8c4e
      antirez authored
      Sentinel was not able to detect slaves when connected to a very recent
      version of Redis master since a previos non-backward compatible change
      to INFO broken the parsing of the slaves ip:port INFO output.
      
      This fixes issue #1164
      4c0f8c4e
  12. 30 Apr, 2013 2 commits
    • 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
    • antirez's avatar
      ef05a78e