- 27 5月, 2013 4 次提交
-
-
由 antirez 提交于
Sending an ACK is now moved into the replicationSendAck() function.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
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.
-
- 25 5月, 2013 3 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
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 提交于
We don't write the output buffer to the client socket for slaves only if the slave is not online.
-
- 18 5月, 2013 1 次提交
-
-
由 antirez 提交于
Should be "continue" and was "return". This fixes issue #1110
-
- 15 5月, 2013 20 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Required because of recent changes in the way logfile is set to standard output.
-
由 antirez 提交于
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.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
- 14 5月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 09 5月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 08 5月, 2013 5 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
The test checks both successful syncs and unsuccessful ones by changing the backlog size.
-
由 antirez 提交于
The test actually worked, but vars for master and slave were inverted and sometimes used incorrectly.
-
由 Jiahao Huang 提交于
bitcount commant may return negtive integer with string length more than 256 MB
-
由 antirez 提交于
-
- 02 5月, 2013 3 次提交
-
-
由 antirez 提交于
This is just to make the code exactly like the above instance used for requirepass. No actual change nor the original code violated the Redis coding style.
-
由 Michel Martens 提交于
-
由 charsyam 提交于
There was a race condition in the AOF rewrite code that, with bad enough timing, could cause a volatile key just about to expire to be turned into a non-volatile key. The bug was never reported to cause actualy issues, but was found analytically by an user in the Redis mailing list: https://groups.google.com/forum/?fromgroups=#!topic/redis-db/Kvh2FAGK4Uk This commit fixes issue #1079.
-
- 30 4月, 2013 2 次提交
-
-
由 antirez 提交于
Tilt mode was too aggressive (not processing INFO output), this resulted in a few problems: 1) Redirections were not followed when in tilt mode. This opened a window to misinform clients about the current master when a Sentinel was in tilt mode and a fail over happened during the time it was not able to update the state. 2) It was possible for a Sentinel exiting tilt mode to detect a false fail over start, if a slave rebooted with a wrong configuration about at the same time. This used to happen since in tilt mode we lose the information that the runid changed (reboot). Now instead the Sentinel in tilt mode will still remove the instance from the list of slaves if it changes state AND runid at the same time. Both are edge conditions but the changes should overall improve the reliability of Sentinel.
-
由 antirez 提交于
-