- 19 Mar, 2013 1 commit
-
-
antirez authored
It's just a simpler way to CLUSTER DELSLOTS with all the slots as arguments, in order to obtain a node without assigned slots for reconfiguration.
-
- 15 Mar, 2013 10 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Redis Cluster can cope with a minority of nodes not informed about the failure of a master in time for some reason (netsplit or node not functioning properly, blocked, ...) however to wait a few seconds before to start the failover will make most "normal" failovers simpler as the FAIL message will propagate before the slave election happens.
-
antirez authored
-
antirez authored
Also, a few nearby comments improved.
-
antirez authored
-
antirez authored
-
antirez authored
See the function top-comment for info why this is useful sometimes.
-
antirez authored
Also don't check for NOADDR as we check that node->link is not NULL that's enough.
-
antirez authored
-
- 14 Mar, 2013 5 commits
- 13 Mar, 2013 7 commits
-
-
antirez authored
-
antirez authored
However currently the control is passed to a function doing nothing at all.
-
antirez authored
-
antirez authored
-
antirez authored
This message is sent by a slave that is ready to failover its master to other nodes to get the authorization from the majority of masters.
-
antirez authored
-
antirez authored
-
- 07 Mar, 2013 3 commits
- 06 Mar, 2013 2 commits
- 05 Mar, 2013 6 commits
-
-
antirez authored
-
antirez authored
If we have a master in FAIL state that's reachable again, and apparently no one is going to serve its slots, clear the FAIL flag and let the cluster continue with its operations again.
-
antirez authored
This is the unix time at which we set the FAIL flag for the node. It is only valid if FAIL is set. The idea is to use it in order to make the cluster more robust, for instance in order to revert a FAIL state if it is long-standing but still slots are assigned to this node, that is, no one is going to fix these slots apparently.
-
antirez authored
-
antirez authored
Usually we try to send just 1 ping every second, however when we detect we are going to have unreliable failure detection because we can't ping some node in time, send an additional ping. This should only happen with very large clusters or when the the node timeout is set to a very low value.
-
antirez authored
-
- 04 Mar, 2013 5 commits
-
-
antirez authored
If we are a cluster node the DB content will not match our configured slots. Don't do the check at all.
-
antirez authored
There are pathological cases where the line can be even longer a single node may contain all the slots in importing/migrating state.
-
antirez authored
-
antirez authored
-
charsyam authored
adding check error code
-
- 28 Feb, 2013 1 commit
-
-
antirez authored
As stated in the comment this is usually due to a resharding in progress so the client should be still redirected to the old node that will handle the redirection elsewhere.
-