1. 07 May, 2019 1 commit
  2. 06 May, 2019 2 commits
  3. 21 Feb, 2019 1 commit
  4. 12 Feb, 2019 1 commit
    • zhaozhao.zz's avatar
      ACL: add masteruser configuration for replication · ea9d3aef
      zhaozhao.zz authored
      In mostly production environment, normal user's behavior should be
      limited.
      
      Now in redis ACL mechanism we can do it like that:
      
          user default on +@all ~* -@dangerous nopass
          user admin on +@all ~* >someSeriousPassword
      
      Then the default normal user can not execute dangerous commands like
      FLUSHALL/KEYS.
      
      But some admin commands are in dangerous category too like PSYNC,
      and the configurations above will forbid replica from sync with master.
      
      Finally I think we could add a new configuration for replication,
      it is masteruser option, like this:
      
          masteruser admin
          masterauth someSeriousPassword
      
      Then replica will try AUTH admin someSeriousPassword and get privilege
      to execute PSYNC. If masteruser is NULL, replica would AUTH with only
      masterauth like before.
      ea9d3aef
  5. 05 Feb, 2019 2 commits
  6. 04 Feb, 2019 3 commits
  7. 21 Jan, 2019 1 commit
  8. 18 Jan, 2019 2 commits
  9. 17 Jan, 2019 1 commit
  10. 09 Jan, 2019 1 commit
  11. 12 Dec, 2018 1 commit
  12. 07 Nov, 2018 1 commit
  13. 21 Oct, 2018 1 commit
  14. 13 Sep, 2018 1 commit
  15. 11 Sep, 2018 2 commits
  16. 05 Sep, 2018 1 commit
  17. 27 Aug, 2018 3 commits
  18. 30 Jul, 2018 1 commit
  19. 23 Jul, 2018 1 commit
  20. 13 Jul, 2018 1 commit
  21. 02 Jul, 2018 1 commit
  22. 27 Jun, 2018 1 commit
  23. 13 Jun, 2018 1 commit
  24. 12 Jun, 2018 1 commit
  25. 09 Jun, 2018 2 commits
  26. 07 Jun, 2018 2 commits
  27. 24 May, 2018 1 commit
  28. 18 Apr, 2018 1 commit
  29. 15 Mar, 2018 1 commit
  30. 14 Mar, 2018 1 commit
    • antirez's avatar
      Cluster: ability to prevent slaves from failing over their masters. · 432bf477
      antirez authored
      This commit, in some parts derived from PR #3041 which is no longer
      possible to merge (because the user deleted the original branch),
      implements the ability of slaves to have a special configuration
      preventing that they try to start a failover when the master is failing.
      
      There are multiple reasons for wanting this, and the feautre was
      requested in issue #3021 time ago.
      
      The differences between this patch and the original PR are the
      following:
      
      1. The flag is saved/loaded on the nodes configuration.
      2. The 'myself' node is now flag-aware, the flag is updated as needed
         when the configuration is changed via CONFIG SET.
      3. The flag name uses NOFAILOVER instead of NO_FAILOVER to be consistent
         with existing NOADDR.
      4. The redis.conf documentation was rewritten.
      
      Thanks to @deep011 for the original patch.
      432bf477