[SERVER-15310] kill all operations before attempting stepdown Created: 18/Sep/14  Updated: 27/Oct/15  Resolved: 01/Dec/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.8.0-rc2

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-16194 Lock manager should expose methods th... Closed
Documented
is documented by DOCS-4349 Document changes to shutdown/stepdown... Closed
Related
related to SERVER-17150 logOp fassert when dropping collectio... Closed
related to SERVER-15308 Stepdown does not cancel active (back... Closed
related to SERVER-17435 Invariant failure when killing user o... Closed
Tested
Backwards Compatibility: Fully Compatible
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 01/Dec/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-15310 Kill all user operations on stepdown.
Branch: master
https://github.com/mongodb/mongo/commit/038ddab4c9144daed30d4c2982d5b3319d551e61

Generated at Thu Feb 08 03:37:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.