- 05 Nov, 2018 7 commits
-
-
artix authored
- clusterManagerFixOpenSlot: ensure that the slot is unassigned before ADDSLOTS - clusterManagerFixSlotsCoverage: after cold migration, the slot configuration is now updated on all the nodes.
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
antirez authored
This bug had a double effect: 1. Sometimes entries may not be emitted, producing broken protocol where the array length was greater than the emitted entires, blocking the client waiting for more data. 2. Some other time the right entry was claimed, but a wrong entry was returned to the client. This fix should correct both the instances.
-
antirez authored
-
- 03 Nov, 2018 1 commit
-
-
michael-grunder authored
This fixes an overflow on 32-bit systems.
-
- 31 Oct, 2018 4 commits
-
-
Guy Korland authored
-
antirez authored
So far it was not possible to setup Sentinel with authentication enabled. This commit introduces this feature: every Sentinel will try to authenticate with other sentinels using the same password it is configured to accept clients with. So for instance if a Sentinel has a "requirepass" configuration statemnet set to "foo", it will use the "foo" password to authenticate with every other Sentinel it connects to. So basically to add the "requirepass" to all the Sentinels configurations is enough in order to make sure that: 1) Clients will require the password to access the Sentinels instances. 2) Each Sentinel will use the same password to connect and authenticate with every other Sentinel in the group. Related to #3279 and #3329.
-
antirez authored
Sentinel must be exposed, so protected mode is just an issue for users in case Redis was started in Sentinel mode. Related to #3279 and #3329.
-
antirez authored
This logs what happens in the context of the fix in PR #5367.
-
- 30 Oct, 2018 1 commit
-
-
antirez authored
Fake clients are used in special situations and are not linked to the normal clients list, freeing them will always result in Redis crashing in one way or the other. It's not common to send replies to fake clients, but we have one usage in the modules API. When a client is blocked, we associate to the blocked client object (that is safe to manipulate in a thread), a fake client that accumulates replies. So because of this bug there was the problem described in issue #5443. The fix was verified to work with the provided example module. To write a regression is very hard and unlikely to be triggered in the future.
-
- 26 Oct, 2018 2 commits
-
-
David Carlier authored
-
David Carlier authored
timezone global is a linux-ism whereas it is a function under BSD. Here a helper to get the timezone value in a more portable manner.
-
- 25 Oct, 2018 2 commits
- 24 Oct, 2018 2 commits
- 22 Oct, 2018 2 commits
- 21 Oct, 2018 1 commit
-
-
hujie authored
-
- 20 Oct, 2018 1 commit
-
-
hujie authored
-
- 19 Oct, 2018 3 commits
-
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
- 18 Oct, 2018 1 commit
-
-
youjiali1995 authored
-
- 17 Oct, 2018 9 commits
-
-
Itamar Haber authored
-
antirez authored
They play better with Lua scripting, otherwise Lua will see status replies as "ok" = "string" which is very odd, and actually as @oranagra reasoned in issue #5456 in the rest of the Redis code base there was no such concern as saving a few bytes when the protocol is emitted.
-
Itamar Haber authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This avoids issues with having to replicate a command that produced errors.
-
antirez authored
-
zhaozhao.zz authored
-
- 16 Oct, 2018 4 commits
-
-
Damien Tournoud authored
-
zhaozhao.zz authored
-
antirez authored
Related to #5426.
-
antirez authored
Related to #5426.
-