- 27 May, 2013 2 commits
-
-
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 4 commits
- 09 May, 2013 2 commits
- 08 May, 2013 6 commits
-
-
antirez authored
-
antirez authored
The test checks both successful syncs and unsuccessful ones by changing the backlog size.
-
antirez authored
The test actually worked, but vars for master and slave were inverted and sometimes used incorrectly.
-
antirez authored
This reverts commit 2c75f2cf. After further analysis, it is very unlikely that we'll raise the string size limit to > 512MB, and at the same time such big strings will be used in 32 bit systems. Better to revert to size_t so that 32 bit processors will not be forced to use a 64 bit counter in normal operations, that is currently completely useless.
-
Salvatore Sanfilippo authored
in 32bit machine, popcount don't work with a input string length up to 5...
-
antirez authored
-
- 07 May, 2013 2 commits
-
-
Jiahao Huang authored
-
Jiahao Huang authored
bitcount commant may return negtive integer with string length more than 256 MB
-
- 03 May, 2013 4 commits
-
-
antirez authored
When the PONG delay is half the cluster node timeout, the link gets disconnected (and later automatically reconnected) in order to ensure that it's not just a dead connection issue. However this operation is only performed if the link is old enough, in order to avoid to disconnect the same link again and again (and among the other problems, never receive the PONG because of that). Note: when the link is reconnected, the 'ping_sent' field is not updated even if a new ping is sent using the new connection, so we can still reliably detect a node ping timeout.
-
antirez authored
-
antirez authored
-
antirez authored
Also clusterBroadcastPing() was renamed into clusterBroadcastPong() that's what the function is actually doing.
-