- 02 12月, 2013 3 次提交
-
-
由 antirez 提交于
See issue #1419.
-
由 antirez 提交于
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 提交于
-
- 30 11月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 29 11月, 2013 1 次提交
-
-
由 antirez 提交于
80 cols friendly, some minor change to the code to make it simpler.
-
- 28 11月, 2013 3 次提交
- 26 11月, 2013 2 次提交
-
-
由 Salvatore Sanfilippo 提交于
fix a bug in sentinel.c about pub/sub link
-
由 huangz1990 提交于
-
- 25 11月, 2013 3 次提交
-
-
由 antirez 提交于
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 提交于
This fixes issue #1395.
-
由 antirez 提交于
Fixes issue #1298.
-
- 22 11月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 21 11月, 2013 8 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This commit introduces a funciton called when Sentinel is ready for normal operations to avoid putting Sentinel specific stuff in redis.c.
-
由 antirez 提交于
Does not fix any bug as the test is performed by the caller, but better to have the check.
-
由 antirez 提交于
-
- 20 11月, 2013 3 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
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.
-
- 19 11月, 2013 12 次提交
-
-
由 antirez 提交于
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 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Also the sentinel configuration rewriting was modified in order to account for failover in progress, where we need to provide the promoted slave address as master address, and the old master address as one of the slaves address.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
- 18 11月, 2013 3 次提交
-
-
由 antirez 提交于
We'll use CONFIG REWRITE (internally) in order to store the new configuration of a Sentinel after the internal state changes. In order to do so, we need configuration options (that usually the user will not touch at all) about config epoch of the master, Sentinels and Slaves known for this master, and so forth.
-
由 antirez 提交于
-
由 antirez 提交于
The time Sentinel waits since the slave is detected to be configured to the wrong master, before reconfiguring it, is now the failover_timeout time as this makes more sense in order to give the Sentinel performing the failover enoung time to reconfigure the slaves slowly (if required by the configuration). Also we now PUBLISH more frequently the new configuraiton as this allows to switch the reapprearing master back to slave faster.
-