Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2016-08-29, Repl 2016-09-19, Repl 2016-10-10, Repl 2016-11-21
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

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

Currently if mongod is shutdown during initialsync, it will wait for initial sync to terminate before finishing. Since the mongod is partially shutdown initial sync will fail and it will wait to fail 10 times before finally failing and shutting down. Rather, when the ReplicationCoordinatorImpl shuts down, it should shut down the data replicator which should tell initial sync to stop with a ShutdownInProgress status.

depends on

SERVER-26999 race between DatabasesCloner::_succeed_inlock and DataReplicator::_doNextActions_InitialSync_inlock() could prevent initial sync from completing

Closed

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-17081 Resync command under write load can fassert

Closed

SERVER-23759 shutting down a node while replication is initializing can crash

Closed

SERVER-26969 add data replicator test case for shutting down immediately after startup

Closed

related to

SERVER-27052 Add asynchronous operation support to DataReplicator

Closed

(1 related to)

Assignee:: Benety Goh
Reporter:: Judah Schvimer
Participants:: Benety Goh, Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Aug 17 2016 03:58:17 PM UTC
Updated:: Jan 25 2017 09:58:11 PM UTC
Resolved:: Nov 15 2016 09:22:05 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates