-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.6, 2.5.2
-
Component/s: Replication
-
Environment:2-node replica set
-
ALL
When the node is doing initial sync and it's in the index build phase, it will not respond to the replSetElect command.
Steps to reproduce:
- setup a one-node replica set
- write a lot of data and create a bunch of indexes
- add a new node
- wait for the new node to go into the the index building phase after all records are cloned
- issue stepDown(3) on the PRIMARY
- observe that the election is delayed until index build is finished
Expected result: to be able to elect a primary if the secondary is doing an initial sync
Rationale: in more complicated scenarios involving multiple servers doing initial sync and network splits, this bug can lead to significant (depending on the actual indexes) delays in elections
- duplicates
-
SERVER-12170 Do not call relinquish() when not vetoing an election
- Closed
- is related to
-
SERVER-11103 replset mutex should be not be held during DB lock attempts
- Closed