- 30 May, 2013 5 commits
- 29 May, 2013 2 commits
-
-
antirez authored
-
antirez authored
There is a new 'lag' information in the list of slaves, in the "replication" section of the INFO output. Also the format was changed in a backward incompatible way in order to make it more easy to parse if new fields are added in the future, as the new format is comma separated but has named fields (no longer positional fields).
-
- 28 May, 2013 1 commit
-
-
antirez authored
-
- 27 May, 2013 9 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Now masters, using the time at which the last REPLCONF ACK was received, are able to explicitly disconnect slaves that are no longer responding. Previously the only chance was to see a very long output buffer, that was highly suboptimal.
-
antirez authored
ACKs can be also used as a base for synchronous replication. However in that case they'll be explicitly requested by the master when the client sends a request that needs to be replicated synchronously.
-
antirez authored
Sending an ACK is now moved into the replicationSendAck() function.
-
antirez authored
-
antirez authored
-
antirez authored
This special command is used by the slave to inform the master the amount of replication stream it currently consumed. it does not return anything so that we not need to consume additional bandwidth needed by the master to reply something. The master can do a number of things knowing the amount of stream processed, such as understanding the "lag" in bytes of the slave, verify if a given command was already processed by the slave, and so forth.
-
- 24 May, 2013 3 commits
-
-
antirez authored
-
antirez authored
When master send commands, there is no need for the slave to reply. Redis used to queue the reply in the output buffer and discard the reply later, this is a waste of work and it is not clear why it was this way (I sincerely don't remember). This commit changes it in order to don't queue the reply at all. All tests passing.
-
antirez authored
We don't write the output buffer to the client socket for slaves only if the slave is not online.
-
- 18 May, 2013 1 commit
-
-
antirez authored
Should be "continue" and was "return". This fixes issue #1110
-
- 15 May, 2013 11 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Required because of recent changes in the way logfile is set to standard output.
-
antirez authored
Also the logfile option was modified to always have an explicit value and to log to stdout when an empty string is used as log file. Previously there was special handling of the string "stdout" that set the logfile to NULL, this always required some special handling.
-
- 14 May, 2013 5 commits
- 13 May, 2013 3 commits