- 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 5 commits
-
-
Anurag Ramdasan authored
-
Anurag Ramdasan authored
-
Anurag Ramdasan authored
-
antirez authored
-
antirez authored
-
- 03 Dec, 2013 2 commits
- 02 Dec, 2013 3 commits
-
-
antirez authored
-
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.
-
- 28 Nov, 2013 4 commits
-
-
antirez authored
From the point of view of the slave not accepting writes from the master can only create a bigger consistency issue.
-
antirez authored
We now have replicationSetMaster() and replicationUnsetMaster() that can be called in other contexts (for instance Redis Cluster).
-
antirez authored
-
antirez authored
-
- 26 Nov, 2013 1 commit
-
-
huangz1990 authored
-
- 25 Nov, 2013 5 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
Deprecate redis copy script 2.8
-
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.
-
- 22 Nov, 2013 1 commit
-
-
antirez authored
-
- 21 Nov, 2013 16 commits
-
-
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
-
antirez authored
-
antirez authored
-
antirez authored
At the end of the file, CONFIG REWRITE adds a comment line that: # Generated by CONFIG REWRITE Followed by the additional config options required. However this was added again and again at every rewrite in praticular conditions (when a given set of options change in a given time during the time). Now if it was alrady encountered, it is not added a second time. This is especially important for Sentinel that rewrites the config at every state change.
-
antirez authored
Some are just to know if the master is down, and in this case the runid in the request is set to "*", others are actually in order to seek for a vote and get elected. In the latter case the runid is set to the runid of the instance seeking for the vote.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-