- 07 May, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 06 May, 2019 2 commits
- 21 Feb, 2019 1 commit
-
-
antirez authored
-
- 12 Feb, 2019 1 commit
-
-
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.
-
- 05 Feb, 2019 2 commits
- 04 Feb, 2019 3 commits
- 21 Jan, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 18 Jan, 2019 2 commits
- 17 Jan, 2019 1 commit
-
-
antirez authored
-
- 09 Jan, 2019 1 commit
-
-
antirez authored
-
- 12 Dec, 2018 1 commit
-
-
antirez authored
Related to issue #5686 and PR #5689.
-
- 07 Nov, 2018 1 commit
-
-
antirez authored
Thanks to @NicolasLM, see issue #5537.
-
- 21 Oct, 2018 1 commit
-
-
hujie authored
-
- 13 Sep, 2018 1 commit
-
-
antirez authored
-
- 11 Sep, 2018 2 commits
- 05 Sep, 2018 1 commit
-
-
antirez authored
See issue #5250 and issue #5292 for more info.
-
- 27 Aug, 2018 3 commits
- 30 Jul, 2018 1 commit
-
-
antirez authored
-
- 23 Jul, 2018 1 commit
-
-
antirez authored
This way we can remember what the user configured HZ is, but change the actual HZ dynamically if needed in the dynamic HZ feature implementation.
-
- 13 Jul, 2018 1 commit
-
-
WuYunlong authored
-
- 02 Jul, 2018 1 commit
-
-
antirez authored
-
- 27 Jun, 2018 1 commit
-
-
Oran Agra authored
-
- 13 Jun, 2018 1 commit
-
-
shenlongxing authored
-
- 12 Jun, 2018 1 commit
-
-
Shen Longxing authored
The active-defrag-threshold-lower/active-defrag-threshold-upper min/max value in redis.conf should be consistent with 'config set' command.
-
- 09 Jun, 2018 2 commits
-
-
Itamar Haber authored
-
shenlongxing authored
-
- 07 Jun, 2018 2 commits
-
-
Itamar Haber authored
-
antirez authored
-
- 24 May, 2018 1 commit
-
-
antirez authored
They failed when active defrag could not be activated because the Jemalloc version does not include the additional APIs.
-
- 18 Apr, 2018 1 commit
-
-
Guy Benoish authored
-
- 15 Mar, 2018 1 commit
-
-
zhaozhao.zz 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.
-