Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.2.9
Affects Version/s: None
Component/s: Replication
Labels:
- code-and-test

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 18 (08/05/16)
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Mathias Stearn
Reporter:: Mathias Stearn
Participants:: Githook User, Mathias Stearn
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jul 29 2016 07:58:58 PM UTC
Updated:: Nov 20 2016 11:28:52 PM UTC
Resolved:: Aug 01 2016 03:40:28 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates