- 04 Sep, 2018 6 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.
-
antirez authored
See reasoning in #5297.
-
dejun.xdj authored
-
Chris Lamb authored
-
zhaozhao.zz authored
-
- 29 Aug, 2018 21 commits
-
-
antirez authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
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
-
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
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
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.
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
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.
-
Chris Lamb authored
See <https://reproducible-builds.org/specs/source-date-epoch/ > for more details. Signed-off-by:
Chris Lamb <chris@chris-lamb.co.uk>
-
Chris Lamb authored
This may look a little pointless (and it is a complete no-op change here) but as package maintainers need to modify these lines to actually daemonize (etc. etc) but it's far preferable if the diff is restricted to actually changing just that bit, not adding docs, etc. The less diff the better, in general. Signed-off-by:
Chris Lamb <chris@chris-lamb.co.uk>
-
dejun.xdj authored
-
shenlongxing authored
-
antirez authored
Realted to #5201.
-
- 03 Aug, 2018 3 commits
- 02 Aug, 2018 10 commits
-
-
antirez authored
Related to #5184.
-
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.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
dejun.xdj authored
-
dejun.xdj authored
If 'mmid_supp' is set to 0, "-" and "+" will be treated as an invalid ID.
-