- 17 Dec, 2013 6 commits
-
-
antirez authored
The value was otherwise undefined, so next time the node was promoted again from slave to master, adding a slave to the list of slaves would likely crash the server or result into undefined behavior.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This prevented 32bit cluster instances from clearing the FAIL flag when needed.
-
antirez authored
Ping sent and pong received fields need to be casted to long long to be printed correctly into 32 bit systems.
-
- 05 Dec, 2013 1 commit
-
-
antirez authored
-
- 02 Dec, 2013 1 commit
-
-
antirez authored
-
- 29 Nov, 2013 2 commits
- 08 Nov, 2013 6 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Now there is a function that handles the update of the local slot configuration every time we have some new info about a node and its set of served slots and configEpoch. Moreoever the UPDATE packets are now processed when received (it was a work in progress in the previous commit).
-
antirez authored
-
antirez authored
The commit also introduces detection of nodes publishing not updated configuration. More work in progress to send an UPDATE packet to inform of the config change.
-
- 05 Nov, 2013 1 commit
-
-
antirez authored
-
- 11 Oct, 2013 1 commit
-
-
antirez authored
-
- 09 Oct, 2013 4 commits
-
-
antirez authored
-
antirez authored
After the change in clusterCron() frequency of call, we still want to ping just one random node every second.
-
antirez authored
All the internal state of cluster involving time is now using mstime_t and mstime() in order to use milliseconds resolution. Also the clusterCron() function is called with a 10 hz frequency instead of 1 hz. The cluster node_timeout must be also configured in milliseconds by the user in redis.conf.
-
antirez authored
-
- 08 Oct, 2013 1 commit
-
-
antirez authored
When a slave requests our vote, the configEpoch he claims for its master and the set of served slots must be greater or equal to the configEpoch of the nodes serving these slots in the current configuraiton of the master granting its vote. In other terms, masters don't vote for slaves having a stale configuration for the slots they want to serve.
-
- 07 Oct, 2013 3 commits
- 03 Oct, 2013 1 commit
-
-
antirez authored
The new API is able to remember operations to perform before returning to the event loop, such as checking if there is the failover quorum for a slave, save and fsync the configuraiton file, and so forth. Because this operations are performed before returning on the event loop we are sure that messages that are sent in the same event loop run will be delivered *after* the configuration is already saved, that is a requirement sometimes. For instance we want to publish a new epoch only when it is already stored in nodes.conf in order to avoid returning back in the logical clock when a node is restarted. This new API provides a big performance advantage compared to saving and possibly fsyncing the configuration file multiple times in the same event loop run, especially in the case of big clusters with tens or hundreds of nodes.
-
- 02 Oct, 2013 3 commits
- 01 Oct, 2013 2 commits
- 30 Sep, 2013 6 commits
-
-
antirez authored
The new algorithm does not check replies time as checking for the currentEpoch in the reply ensures that the reply is about the current election process.
-
antirez authored
-
antirez authored
The old algorithm used a PROMOTED flag and explicitly checks about slave->master convertions. Wit the new cluster meta-data propagation algorithm we just look at the configEpoch to check if we need to reconfigure slots, then: 1) If a node is a master but it reaches zero served slots becuase of reconfiguration. 2) If a node is a slave but the master reaches zero served slots because of a reconfiguration. We switch as a replica of the new slots owner.
-
antirez authored
We need to: 1) Increment the configEpoch. 2) Save it to disk and fsync the file. 3) Broadcast the PONG with the new configuration. If other nodes will receive the updated configuration we need to be sure to restart with this new config in the event of a crash.
-
antirez authored
-
antirez authored
-
- 27 Sep, 2013 1 commit
-
-
antirez authored
-
- 26 Sep, 2013 1 commit
-
-
antirez authored
-