1. 11 Sep, 2018 1 commit
    • antirez's avatar
      Slave removal: remove slave from sentinel.conf when possible. · f74c7394
      antirez authored
      All the occurrences translated, but the ones referring to SLAVEOF
      must be intact because that describe the actual Sentinel -> Redis
      protocol. In theory we could send REPLICAOF to Redis instances, but
      actually this would prevent Sentinel to be compatible with older Redis
      instances.
      f74c7394
  2. 27 Aug, 2018 1 commit
  3. 25 Jun, 2018 1 commit
  4. 14 Jun, 2018 1 commit
    • antirez's avatar
      Sentinel: add an option to deny online script reconfiguration. · 6a66b93b
      antirez authored
      The ability of "SENTINEL SET" to change the reconfiguration script at
      runtime is a problem even in the security model of Redis: any client
      inside the network may set any executable to be ran once a failover is
      triggered.
      
      This option adds protection for this problem: by default the two
      SENTINEL SET subcommands modifying scripts paths are denied. However the
      user is still able to rever that using the Sentinel configuration file
      in order to allow such a feature.
      6a66b93b
  5. 11 Aug, 2016 1 commit
  6. 16 Jan, 2015 1 commit
  7. 29 Sep, 2014 1 commit
  8. 04 Sep, 2014 2 commits
  9. 26 May, 2014 1 commit
  10. 12 May, 2014 1 commit
  11. 07 Mar, 2014 1 commit
  12. 11 Dec, 2013 1 commit
  13. 21 Nov, 2013 1 commit
  14. 19 Jan, 2013 1 commit
  15. 16 Jan, 2013 1 commit
  16. 26 Sep, 2012 1 commit
  17. 02 Aug, 2012 1 commit
    • antirez's avatar
      Sentinel: client reconfiguration script execution. · 6275004c
      antirez authored
      This commit adds support to optionally execute a script when one of the
      following events happen:
      
      * The failover starts (with a slave already promoted).
      * The failover ends.
      * The failover is aborted.
      
      The script is called with enough parameters (documented in the example
      sentinel.conf file) to provide information about the old and new ip:port
      pair of the master, the role of the sentinel (leader or observer) and
      the name of the master.
      
      The goal of the script is to inform clients of the configuration change
      in a way specific to the environment Sentinel is running, that can't be
      implemented in a genereal way inside Sentinel itself.
      6275004c
  18. 31 Jul, 2012 1 commit
  19. 28 Jul, 2012 1 commit
  20. 25 Jul, 2012 3 commits
  21. 23 Jul, 2012 3 commits