- 30 Aug, 2018 2 commits
-
-
antirez authored
Processing command from the master while the slave is in busy state is not correct, however we cannot, also, just reply -BUSY to the replication stream commands from the master. The correct solution is to stop processing data from the master, but just accumulate the stream into the buffers and resume the processing later. Related to #5297.
-
antirez authored
However the master scripts will be impossible to kill. Related to #5297.
-
- 29 Aug, 2018 7 commits
-
-
antirez authored
See reasoning in #5297.
-
Salvatore Sanfilippo authored
Correct "did not received" -> "did not receive" typos/grammar.
-
Salvatore Sanfilippo authored
remove duplicate bind in sentinel.conf
-
Salvatore Sanfilippo authored
Supplement to PR #4835, just take info/memory/command as random commands
-
zhaozhao.zz authored
-
Salvatore Sanfilippo authored
some commands' flags should be set correctly, issue #4834
-
zhaozhao.zz authored
-
- 27 Aug, 2018 8 commits
-
-
Salvatore Sanfilippo authored
Fix unstable tests on slow machines.
-
antirez authored
-
antirez authored
-
antirez authored
Note: this breaks backward compatibility with Redis 4, since now slaves by default are exact copies of masters and do not try to evict keys independently.
-
antirez authored
-
antirez authored
-
antirez authored
-
zhaozhao.zz authored
-
- 26 Aug, 2018 6 commits
-
-
Salvatore Sanfilippo authored
rewrite BRPOPLPUSH as RPOPLPUSH to propagate
-
Salvatore Sanfilippo authored
pipeline: do not sdsrange querybuf unless all commands processed
-
Chris Lamb authored
-
Salvatore Sanfilippo authored
Use SOURCE_DATE_EPOCH over unreproducible uname + date calls.
-
Salvatore Sanfilippo authored
Tidy grammar in CONFIG SET maxmemory warning.
-
Salvatore Sanfilippo authored
Make some defaults explicit in the sentinel.conf for package maintainers
-
- 25 Aug, 2018 1 commit
-
-
Chris Lamb authored
-
- 23 Aug, 2018 1 commit
-
-
zhaozhao.zz authored
Function setProtocolError just records proctocol error details in server log, set client as CLIENT_CLOSE_AFTER_REPLY. It doesn't care about querybuf sdsrange, because we will do it after procotol parsing.
-
- 21 Aug, 2018 1 commit
-
-
Oran Agra authored
Few tests had borderline thresholds that were adjusted. The slave buffers test had two issues, preventing the slave buffer from growing: 1) the slave didn't necessarily go to sleep on time, or woke up too early, now using SIGSTOP to make sure it goes to sleep exactly when we want. 2) the master disconnected the slave on timeout
-
- 14 Aug, 2018 4 commits
-
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
- 13 Aug, 2018 2 commits
-
-
zhaozhao.zz authored
-
zhaozhao.zz authored
This is an optimization for processing pipeline, we discussed a problem in issue #5229: clients may be paused if we apply `CLIENT PAUSE` command, and then querybuf may grow too large, the cost of memmove in sdsrange after parsing a completed command will be horrible. The optimization is that parsing all commands in queyrbuf , after that we can just call sdsrange only once.
-
- 03 Aug, 2018 4 commits
-
-
Salvatore Sanfilippo authored
Streams: ID of xclaim command should start from the sixth argument.
-
Salvatore Sanfilippo authored
Fix stream command paras
-
shenlongxing authored
-
antirez authored
Realted to #5201.
-
- 02 Aug, 2018 3 commits
- 01 Aug, 2018 1 commit
-
-
antirez authored
When the element new score is the same of prev/next node, the lexicographical order kicks in, so we can safely update the node in place only when the new score is strictly between the adjacent nodes but never equal to one of them. Technically speaking we could do extra checks to make sure that even if the score is the same as one of the adjacent nodes, we can still update on place, but this rarely happens, so probably not a good deal to make it more complex. Related to #5179.
-