Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.3.14
Affects Version/s: None
Component/s: Replication
Labels:
- Idempotency

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2016-09-19, Repl 2016-10-10
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

Currently if the applier has an error it will fassert and terminate the mongod. Some errors should probably be ignored and some should lead to a restart of initial sync.

One example is here where an IndexOptionsConflict error led to an fassert. If this error had been ignored it probably would have been fine. Alternatively initial sync could have just restarted.
https://logkeeper.mongodb.org/build/a3f0586facc3aafcdb1719977208c783/test/579fe5a89041300d28023a18

At the very least we should restart initial sync on errors like this.

is depended on by

SERVER-25068 Make small_oplog_rs_initsync passthrough test to run initial sync while the primary is operating on its data

Closed

is related to

SERVER-25332 Initial sync bootstrap needs to handle collection metadata changes idempotently

Closed

Assignee:: Siyuan Zhou
Reporter:: Judah Schvimer
Participants:: Eric Milkie, Githook User, Judah Schvimer, Siyuan Zhou
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Aug 02 2016 06:00:47 PM UTC
Updated:: Jan 25 2017 09:58:20 PM UTC
Resolved:: Sep 21 2016 10:15:47 PM UTC
Confidence Status Last Update:: 19/Sep/16 3:16 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates