Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.8.0-rc2
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible

Since stepdown requires a global shared lock, it will block waiting possibly a very long time if there are long running write operations with a document-level-locking storage engine. Such write operations could be things like map/reduce or index builds. We should kill those operations before attempting to enqueue the global shared lock.

depends on

SERVER-16194 Lock manager should expose methods that separate enqueuing a lock request and waiting for it to be satisfied

Closed

is documented by

DOCS-4349 Document changes to shutdown/stepdown in replication

Closed

related to

SERVER-17150 logOp fassert when dropping collection on stepped-down primary

Closed

SERVER-15308 Stepdown does not cancel active (background) index builds causing shutdown on completion

Closed

SERVER-17435 Invariant failure when killing user ops during stepdown

Closed

Assignee:: Spencer Brody (Inactive)

Reporter:: Scott Hernandez (Inactive)

Participants:: Githook User, Scott Hernandez, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: Sep 18 2014 05:46:27 PM UTC

Updated:: Oct 27 2015 02:24:51 PM UTC

Resolved:: Dec 01 2014 09:37:29 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates