Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Minor Change
Operating System:
ALL
Sprint:
Repl 2017-04-17, Repl 2017-05-08, Repl 2017-05-29, Repl 2017-06-19, Repl 2017-07-31, Repl 2017-08-21, Repl 2017-09-11, Repl 2017-10-02
Linked BF Score:
0

Currently the stepdown command runs with the global lock in shared mode, which violates the concurrency rules for the _canAcceptNonLocalWrites variable.

is depended on by

SERVER-27892 Clarify locking rules for _canAcceptNonLocalWrites and _canServeNonLocalReads

Closed

is documented by

DOCS-10844 Stepdown command must take global lock in exclusive mode (SERVER-28544)

Closed

is related to

SERVER-28702 Race condition of stepdown command and signaling stepdown waiter

Closed

SERVER-30852 Force reconfig that makes current primary unelectable can result in stepdown without taking the global lock

Closed

related to

SERVER-31223 fix race in StepDownTest::OnlyOneStepDownCmdIsAllowedAtATime

Closed

SERVER-30719 Fix dbCheck behavior during stepdown

Closed

(1 related to)

Assignee:: Spencer Brody (Inactive)

Reporter:: Spencer Brody (Inactive)

Participants:: Githook User, Ramon Fernandez Marina, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: Mar 29 2017 08:13:53 PM UTC

Updated:: May 10 2018 05:26:15 PM UTC

Resolved:: Sep 25 2017 08:50:03 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates