Cluster: check that configEpoch never goes back.

Since there are ways to alter the configEpoch outside of the failover
procedure (for exampel CLUSTER SET-CONFIG-EPOCH and via the configEpoch
collision resolution algorithm), make always sure, before replacing our
configEpoch with a new one, that it is greater than the current one.
This commit is contained in:
antirez 2014-06-07 14:37:09 +02:00
parent a2c2ef7de5
commit 32d0a79f78

View File

@ -2516,7 +2516,8 @@ void clusterHandleSlaveFailover(void) {
}
/* 3) Update my configEpoch to the epoch of the election. */
myself->configEpoch = server.cluster->failover_auth_epoch;
if (myself->configEpoch < server.cluster->failover_auth_epoch)
myself->configEpoch = server.cluster->failover_auth_epoch;
/* 4) Update state and save config. */
clusterUpdateState();