- 20 Mar, 2019 1 commit
-
-
Oran Agra authored
in diskless replication - master was not notifing the slave that rdb transfer terminated on error, and lets slave wait for replication timeout
-
- 18 Mar, 2019 2 commits
- 16 Mar, 2019 1 commit
-
-
antirez authored
-
- 15 Mar, 2019 3 commits
-
-
antirez authored
-
antirez authored
-
John Sully authored
-
- 14 Mar, 2019 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
Guy Benoish authored
-
- 13 Mar, 2019 2 commits
-
-
zhaozhao.zz authored
-
swilly22 authored
-
- 12 Mar, 2019 4 commits
-
-
Steve Webster authored
-
artix authored
Fixes issue #5912
-
vattezhang authored
-
chendianqiang authored
-
- 11 Mar, 2019 1 commit
-
-
swilly22 authored
-
- 10 Mar, 2019 2 commits
- 09 Mar, 2019 1 commit
-
-
John Sully authored
-
- 08 Mar, 2019 2 commits
-
-
Steve Webster authored
The XCLAIM docs state the XCLAIM increments the delivery counter for messages. This PR makes the code match the documentation - which seems like the desired behaviour - whilst still allowing RETRYCOUNT to be specified manually. My understanding of the way streamPropagateXCLAIM() works is that this change will safely propagate to replicas since retry count is pulled directly from the streamNACK struct. Fixes #5194
-
artix authored
-
- 07 Mar, 2019 5 commits
-
-
zhaozhao.zz authored
-
Yuan Zhou authored
hashTypeTryObjectEncoding() is not used now
-
artix authored
-
artix authored
Fix issue #5891
-
Brad Solomon authored
On `make uninstall`, removes: - /usr/local/bin/redis-benchmark - /usr/local/bin/redis-check-aof - /usr/local/bin/redis-check-rdb - /usr/local/bin/redis-cli - /usr/local/bin/redis-sentinel - /usr/local/bin/redis-server (Only the src/ versions are removed in `make clean`)
-
- 06 Mar, 2019 1 commit
-
-
artix authored
-
- 05 Mar, 2019 1 commit
-
-
antirez authored
-
- 04 Mar, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 03 Mar, 2019 1 commit
-
-
Itamar Haber authored
-
- 02 Mar, 2019 1 commit
-
-
antirez authored
Fix #5790 and 5878. Maybe a better option was to have such fields named with the first byte '%' as those are info fields for specification, however now to break it in a backward incompatible way is not an option, so let's use the fields actively to provide info when sensible, otherwise ignore when they are not really helpful.
-
- 01 Mar, 2019 7 commits