gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Cluster: check that configEpoch never goes back.

Browse Source 
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 b732d42a80
commit cff2c3661a
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/cluster.c
View File

@ -2516,7 +2516,8 @@ void clusterHandleSlaveFailover(void) {
} }
/* 3) Update my configEpoch to the epoch of the election. */ /* 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. */ /* 4) Update state and save config. */
clusterUpdateState(); clusterUpdateState();