- 02 Oct, 2013 3 commits
- 01 Oct, 2013 2 commits
- 30 Sep, 2013 8 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
-
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 4 commits
- 25 Sep, 2013 7 commits
- 20 Sep, 2013 2 commits
-
-
antirez authored
First change: now there is no need to be a master in order to detect a failure, however the majority of masters signaling PFAIL or FAIL is needed. This change is important because it allows slaves rejoining the cluster after a partition to sense the FAIL condition so that eventually all the nodes agree on failures.
-
antirez authored
The time is sent in requests, and copied back in reply packets. This way the receiver can compare the time field in a reply with its local clock and check the age of the request associated with this reply. This is an easy way to discard delayed replies. Note that only a clock is used here, that is the one of the node sending the packet. The receiver only copies the field back into the reply, so no synchronization is needed between clocks of different hosts.
-
- 17 Sep, 2013 1 commit
-
-
antirez authored
-
- 04 Sep, 2013 6 commits
-
-
antirez authored
-
antirez authored
Handshake nodes should turn into normal nodes or be freed in a reasonable amount of time, otherwise they'll keep accumulating if the address they are associated with is not reachable for some reason.
-
antirez authored
The code freed a reply object that was never created, resulting in a segfault every time randomkey returned a key that was deleted before we queried it for size.
-
antirez authored
-
antirez authored
-
antirez authored
-
- 03 Sep, 2013 5 commits
-
-
Maxim Zakharov authored
-
Maxim Zakharov authored
-
antirez authored
-
antirez authored
-
antirez authored
The code used to copy the header *after* the 'hdr' pointer was already switched to the new buffer. Of course we need to do the reverse.
-
- 30 Aug, 2013 1 commit
-
-
antirez authored
-