- 11 Nov, 2013 1 commit
-
-
antirez authored
-
- 08 Nov, 2013 6 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Now there is a function that handles the update of the local slot configuration every time we have some new info about a node and its set of served slots and configEpoch. Moreoever the UPDATE packets are now processed when received (it was a work in progress in the previous commit).
-
antirez authored
-
antirez authored
The commit also introduces detection of nodes publishing not updated configuration. More work in progress to send an UPDATE packet to inform of the config change.
-
- 07 Nov, 2013 2 commits
- 06 Nov, 2013 6 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
AUTH and SCRIPT KILL were sent without incrementing the pending commands counter. Clearly this needs some kind of wrapper doing it for the caller in order to be less bug prone.
-
antirez authored
This change makes Sentinel less fragile about a number of failure modes. This commit also fixes a different bug as a side effect, SLAVEOF command was sent multiple times without incrementing the pending commands count.
-
Salvatore Sanfilippo authored
Deprecate utils/redis-copy.rb in favor of redis-copy gem
-
Ryan Biesemeyer authored
-
- 05 Nov, 2013 10 commits
-
-
antirez authored
Thanks to @badboy for reporting it.
-
antirez authored
The previous implementation of SCAN parsed the cursor in the generic function implementing SCAN, SSCAN, HSCAN and ZSCAN. The actual higher-level command implementation only checked for empty keys and return ASAP in that case. The result was that inverting the arguments of, for instance, SSCAN for example and write: SSCAN 0 key Instead of SSCAN key 0 Resulted into no error, since 0 is a non-existing key name very likely. Just the iterator returned no elements at all. In order to fix this issue the code was refactored to extract the function to parse the cursor and return the error. Every higher level command implementation now parses the cursor and later checks if the key exist or not.
-
antirez authored
The previous implementation assumed that the first call always happens with cursor set to 0, this may not be the case, and we want to return 0 anyway otherwise the (broken) client code will loop forever.
-
antirez authored
-
antirez authored
-
antirez authored
This fixes issue #1360 and #1362.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 31 Oct, 2013 4 commits
- 30 Oct, 2013 6 commits
- 28 Oct, 2013 5 commits