-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.2.0
-
Component/s: Replication
-
None
-
ALL
A node that is initial syncing is in state STARTUP2. If all goes well, it transitions to state SECONDARY, then RECOVERING, then back to SECONDARY. The first SECONDARY state is a mistake; it should go straight to RECOVERING.
- is related to
-
SERVER-7186 Batched oplog application increases frequency of idempotency violations
- Closed
- related to
-
SERVER-3251 Overflowed replica set members briefly re-initialize as SECONDARY
- Closed