[SERVER-20036] Add interruption points to operations that hold distributed locks for a long time Created: 19/Aug/15  Updated: 25/Jan/17  Resolved: 21/Jan/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.2.3, 3.3.1

Type: Improvement Priority: Major - P3
Reporter: Andy Schwerin Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: code-only, csrsupgrade
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-22524 Only interrupt mapReduce on catalog m... Closed
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: Sharding 9 (09/18/15), Sharding E (01/08/16), Sharding F (01/29/16)
Participants:
Linked BF Score: 0

 Description   

Operations in sharding that hold distributed locks for a long time without contacting the config server, such as chunk migration, need to periodically confirm that the config servers have not been converted from SCCC to CSRS or vice versa. Such upgrades and downgrades ensure that these operations will eventually fail, but if the node does not check during the operation, it may prevent other new operations from making progress, since it blocks the local node from switching out its catalog manager implementation.



 Comments   
Comment by Githook User [ 21/Jan/16 ]

Author:

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

Message: SERVER-20036 Add back line that was accidentally removed

(cherry picked from commit 6139a33b400ecd23ee8536da74232f70df0f76c6)
Branch: v3.2
https://github.com/mongodb/mongo/commit/187028f283545496b0254216d17822211fe5202c

Comment by Githook User [ 21/Jan/16 ]

Author:

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

Message: SERVER-20036 Add back line that was accidentally removed
Branch: master
https://github.com/mongodb/mongo/commit/6139a33b400ecd23ee8536da74232f70df0f76c6

Comment by Githook User [ 21/Jan/16 ]

Author:

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

Message: SERVER-20036 Interrupt mapReduce and movePrimary commands on catalog manager change

(cherry picked from commit 38740c56f64ba791a681885737f975eb79640a0a)
Branch: v3.2
https://github.com/mongodb/mongo/commit/30175156315dba495454d8c1a81ccdc1ea564416

Comment by Githook User [ 21/Jan/16 ]

Author:

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

Message: SERVER-20036 Interrupt mapReduce and movePrimary commands on catalog manager change
Branch: master
https://github.com/mongodb/mongo/commit/38740c56f64ba791a681885737f975eb79640a0a

Comment by Githook User [ 04/Sep/15 ]

Author:

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

Message: SERVER-20036 Interrupt migrations if there is a pending need to swap active catalog managers
Branch: master
https://github.com/mongodb/mongo/commit/16f9795da51d4a8b2e8c33fcedd66a662f2c069c

Comment by Spencer Brody (Inactive) [ 03/Sep/15 ]

It doesn't look like there's any real way to interrupt the movePrimary or mapReduce commands as they take the distlock in mongos but perform most of their work on mongod

Comment by Githook User [ 03/Sep/15 ]

Author:

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

Message: SERVER-20268 SERVER-20036 DistLockCatalog should get electionId from serverStatus not $gleStats
Branch: master
https://github.com/mongodb/mongo/commit/0307cfaebd6adfe8c9d7554c9ca585e353d261d1

Comment by Githook User [ 02/Sep/15 ]

Author:

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

Message: SERVER-20036 Make moveChunk return meaningful error codes
Branch: master
https://github.com/mongodb/mongo/commit/460f4236c21281059eb5ae91a357d9661c9477d9

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