- 05 Mar, 2020 2 commits
- 25 Sep, 2019 1 commit
-
-
antirez authored
See for reference PR #6337. Thanks to @git-hulk for spotting this.
-
- 13 May, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 13 Mar, 2019 1 commit
-
-
chendianqiang authored
-
- 22 Oct, 2018 2 commits
-
-
antirez authored
-
youjiali1995 authored
-
- 03 Oct, 2018 4 commits
- 14 Sep, 2018 1 commit
-
-
antirez authored
-
- 02 Aug, 2018 2 commits
-
-
antirez authored
-
shenlongxing authored
-
- 30 Jul, 2018 3 commits
- 03 Jul, 2018 1 commit
-
-
Jack Drogon authored
-
- 02 Jul, 2018 1 commit
-
-
antirez authored
-
- 24 Jun, 2018 1 commit
-
-
Guy Benoish authored
-
- 20 Jun, 2018 1 commit
-
-
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.
-
- 19 Jun, 2018 1 commit
-
-
antirez authored
-
- 12 Jun, 2018 2 commits
-
-
antirez authored
-
shenlongxing authored
-
- 09 Jun, 2018 1 commit
-
-
Itamar Haber authored
-
- 07 Jun, 2018 2 commits
-
-
Itamar Haber authored
-
antirez authored
-
- 06 Jun, 2018 1 commit
-
-
shenlongxing authored
-
- 30 Mar, 2018 1 commit
-
-
antirez authored
-
- 29 Mar, 2018 1 commit
-
-
antirez authored
-
- 14 Mar, 2018 1 commit
-
-
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.
-
- 01 Mar, 2018 1 commit
-
-
charsyam authored
-
- 27 Feb, 2018 1 commit
-
-
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.
-
- 18 Jan, 2018 1 commit
-
-
antirez authored
-
- 09 Jan, 2018 1 commit
-
-
antirez authored
See PR #2507. This is a reimplementation of the fix that contained different problems.
-
- 13 Dec, 2017 1 commit
-
-
antirez authored
Fix #3665.
-
- 06 Dec, 2017 1 commit
-
-
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.
-
- 03 Dec, 2017 1 commit
-
-
Itamar Haber authored
-
- 31 Oct, 2017 1 commit
-
-
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.
-
- 27 Jul, 2017 1 commit
-
-
Shaun Webb authored
-