- 06 Dec, 2013 3 commits
-
-
antirez authored
The way the role change was recoded was not sane and too much convoluted, causing the role information to be not always updated. This commit fixes issue #1445.
-
antirez authored
When there is a master address switch, the reported role must be set to master so that we have a chance to re-sample the INFO output to check if the new address is reporting the right role. Otherwise if the role was wrong, it will be sensed as wrong even after the address switch, and for enough time according to the role change time, for Sentinel consider the master SDOWN. This fixes isue #1446, that describes the effects of this bug in practice.
-
antirez authored
-
- 05 Dec, 2013 9 commits
-
-
Salvatore Sanfilippo authored
Grammar fix.
-
Anurag Ramdasan authored
-
Salvatore Sanfilippo authored
fixed typo
-
Anurag Ramdasan authored
-
Salvatore Sanfilippo authored
Fixed grammar: 'usually' to 'usual'
-
Anurag Ramdasan authored
-
antirez authored
-
antirez authored
-
antirez authored
During the refactoring of blocking operations, commit 82b672f6, a bug was introduced where a milliseconds time is compared to a seconds time, so all the clients always appear to timeout if timeout is set to non-zero value. Thanks to Jonathan Leibiusky for finding the bug and helping verifying the cause and fix.
-
- 04 Dec, 2013 1 commit
-
-
antirez authored
-
- 03 Dec, 2013 4 commits
- 02 Dec, 2013 3 commits
-
-
antirez authored
See issue #1419.
-
antirez authored
Sentinels are now desynchronized in a better way changing the time handler frequency between 10 and 20 HZ. This way on average a desynchronization of 25 milliesconds is produced that should be larger enough compared to network latency, avoiding most split-brain condition during the vote. Now that the clocks are desynchronized, to have larger random delays when performing operations can be easily achieved in the following way. Take as example the function that starts the failover, that is called with a frequency between 10 and 20 HZ and will start the failover every time there are the conditions. By just adding as an additional condition something like rand()%4 == 0, we can amplify the desynchronization between Sentinel instances easily. See issue #1419.
-
antirez authored
-
- 29 Nov, 2013 2 commits
- 28 Nov, 2013 3 commits
- 26 Nov, 2013 2 commits
-
-
Salvatore Sanfilippo authored
fix a bug in sentinel.c about pub/sub link
-
huangz1990 authored
-
- 25 Nov, 2013 3 commits
-
-
antirez authored
The result of this one-char bug was pretty serious, if the new master had the same port of the previous master, but just a different IP address, non-leader Sentinels would not be able to recognize the configuration change. This commit fixes issue #1394. Many thanks to @shanemadden that reported the bug and helped investigating it.
-
antirez authored
This fixes issue #1395.
-
antirez authored
Fixes issue #1298.
-
- 21 Nov, 2013 9 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This commit introduces a funciton called when Sentinel is ready for normal operations to avoid putting Sentinel specific stuff in redis.c.
-
antirez authored
Does not fix any bug as the test is performed by the caller, but better to have the check.
-
antirez authored
-
- 20 Nov, 2013 1 commit
-
-
antirez authored
-