-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl 18 (08/05/16)
This ensures that they can go directly to SECONDARY without needing to contact other nodes. This is an extension of SERVER-24933 which made shutdown only happen between batches but could leave the secondary in a state where it had to fetch and apply a batch before reaching SECONDARY state.
This ticket is for the 3.2 work which is being done first. The forward-port to 3.4/master will be ticketed separately.
- is duplicated by
-
SERVER-25773 Upgrade from 3.0.9 to 3.2.9 discards oplog and can't catch up
- Closed
- related to
-
SERVER-24933 Clean shutdown of secondaries should occur in between oplog batches, not during
- Closed