- 13 Mar, 2019 5 commits
-
-
Salvatore Sanfilippo authored
Increment delivery counter on XCLAIM unless RETRYCOUNT specified
-
Salvatore Sanfilippo authored
document additional flag of RM_GetContextFlags
-
Salvatore Sanfilippo authored
Fix compile some warnings
-
zhaozhao.zz authored
-
swilly22 authored
-
- 12 Mar, 2019 8 commits
-
-
Steve Webster authored
-
Salvatore Sanfilippo authored
Added millisecond resolution for blpop command && friends
-
Salvatore Sanfilippo authored
fix a bufferoverflow bug
-
Salvatore Sanfilippo authored
Cluster Manager: add importing/migrating nodes to backup info
-
Salvatore Sanfilippo authored
try lazyfree temp set in SUNION & SDIFF
-
Salvatore Sanfilippo authored
Extend REDISMODULE_CTX_FLAGS to indicate if command was sent by master
-
Salvatore Sanfilippo authored
remove temp-rewriteaof-xxx.aof when interrupt aofrewrite
-
chendianqiang authored
-
- 11 Mar, 2019 1 commit
-
-
swilly22 authored
-
- 10 Mar, 2019 3 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
Replicas aren't allowed to run the replicaof command
-
wurongxin authored
-
- 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
-
Salvatore Sanfilippo authored
server.h: remove dead code
-
- 07 Mar, 2019 2 commits
-
-
zhaozhao.zz authored
-
Yuan Zhou authored
hashTypeTryObjectEncoding() is not used now
-
- 06 Mar, 2019 1 commit
-
-
artix authored
-
- 05 Mar, 2019 1 commit
-
-
antirez authored
-
- 04 Mar, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 02 Mar, 2019 2 commits
-
-
antirez authored
-
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 13 commits
-
-
Salvatore Sanfilippo authored
Cluster Manager (redis-cli): new "backup" command
-
Salvatore Sanfilippo authored
Redis benchmark: multithread support and cluster support
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
-
artix authored
- MOVED or ASK replies are now handled in cluster mode. - Only the first slot per node is used in cluster mode. - Mutlithreading: reduced usage of mutexes in favor of atomic vars.
-
artix authored
-
artix authored
-