1. 18 Sep, 2019 1 commit
  2. 02 Sep, 2019 1 commit
  3. 23 Jul, 2019 1 commit
  4. 15 Mar, 2019 1 commit
  5. 01 Mar, 2019 1 commit
  6. 09 Jan, 2019 2 commits
  7. 22 Oct, 2018 1 commit
  8. 18 Oct, 2018 1 commit
  9. 19 Sep, 2018 4 commits
  10. 11 Sep, 2018 1 commit
  11. 31 Jul, 2018 2 commits
  12. 24 Jul, 2018 2 commits
  13. 21 Jul, 2018 1 commit
  14. 03 Jul, 2018 1 commit
  15. 02 Jul, 2018 1 commit
  16. 24 Jun, 2018 1 commit
  17. 20 Jun, 2018 1 commit
    • Guy Benoish's avatar
      Enhance RESTORE with RDBv9 new features · b5197f1f
      Guy Benoish authored
      RESTORE now supports:
      1. Setting LRU/LFU
      2. Absolute-time TTL
      
      Other related changes:
      1. RDB loading will not override LRU bits when RDB file
         does not contain the LRU opcode.
      2. RDB loading will not set LRU/LFU bits if the server's
         maxmemory-policy does not match.
      b5197f1f
  18. 19 Jun, 2018 1 commit
  19. 09 Jun, 2018 1 commit
  20. 07 Jun, 2018 2 commits
  21. 06 Jun, 2018 1 commit
  22. 30 Mar, 2018 1 commit
  23. 29 Mar, 2018 1 commit
  24. 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
  25. 01 Mar, 2018 1 commit
  26. 27 Feb, 2018 1 commit
    • antirez's avatar
      Cluster: improve crash-recovery safety after failover auth vote. · 533d0e03
      antirez authored
      Add AE_BARRIER to the writable event loop so that slaves requesting
      votes can't be served before we re-enter the event loop in the next
      iteration, so clusterBeforeSleep() will fsync to disk in time.
      Also add the call to explicitly fsync, given that we modified the last
      vote epoch variable.
      533d0e03
  27. 18 Jan, 2018 1 commit
  28. 09 Jan, 2018 1 commit
  29. 13 Dec, 2017 1 commit
  30. 06 Dec, 2017 1 commit
    • antirez's avatar
      Change indentation and other minor details of PR #4489. · 522760fa
      antirez authored
      The main change introduced by this commit is pretending that help
      arrays are more text than code, thus indenting them at level 0. This
      improves readability, and is an old practice when defining arrays of
      C strings describing text.
      
      Additionally a few useless return statements are removed, and the HELP
      subcommand capitalized when printed to the user.
      522760fa
  31. 03 Dec, 2017 1 commit
  32. 31 Oct, 2017 1 commit
    • antirez's avatar
      Fix buffer overflows occurring reading redis.conf. · ffcf7d5a
      antirez authored
      There was not enough sanity checking in the code loading the slots of
      Redis Cluster from the nodes.conf file, this resulted into the
      attacker's ability to write data at random addresses in the process
      memory, by manipulating the index of the array. The bug seems
      exploitable using the following techique: the config file may be altered so
      that one of the nodes gets, as node ID (which is the first field inside the
      structure) some data that is actually executable: then by writing this
      address in selected places, this node ID part can be executed after a
      jump. So it is mostly just a matter of effort in order to exploit the
      bug. In practice however the issue is not very critical because the
      bug requires an unprivileged user to be able to modify the Redis cluster
      nodes configuration, and at the same time this should result in some
      gain. However Redis normally is unprivileged as well. Yet much better to
      have this fixed indeed.
      
      Fix #4278.
      ffcf7d5a
  33. 27 Jul, 2017 1 commit