[SERVER-20037] Transfer responsibility for the release of distributed locks to new catalog manager Created: 19/Aug/15  Updated: 25/Jan/17  Resolved: 12/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:
Duplicate
is duplicated by SERVER-20018 After swapping catalog manager, clean... Closed
Related
related to SERVER-21660 serverStatus can stall and trigger ti... Closed
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: Sharding 9 (09/18/15), Sharding E (01/08/16), Sharding F (01/29/16)
Participants:

 Description   

When replacing the actual sharding catalog manager in a mongo process, the old manager will shut down without being able to release any distributed locks it holds. The new manager should release all locks held by the old manager, since all operations undertaken by the old manager that are not yet complete must have been aborted.



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

Author:

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

Message: SERVER-20037 After CatalogManager swap release distributed locks held by old CatalogManager

(cherry picked from commit f2d33bbcde359f5caf2e4e66559dcc46b164cd2b)
Branch: v3.2
https://github.com/mongodb/mongo/commit/302072ddf3bcd173b23d3c1544b7c6e39d01c259

Comment by Githook User [ 14/Jan/16 ]

Author:

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

Message: SERVER-20037 Clean up calculation of legacy distributed lock process ID

(cherry picked from commit dd0e551071e7128d48d01455e332e30beaa63244)
Branch: v3.2
https://github.com/mongodb/mongo/commit/6c11f9de767a2e8edb50c0ef45f4bebed4b38688

Comment by Githook User [ 12/Jan/16 ]

Author:

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

Message: SERVER-20037 After CatalogManager swap release distributed locks held by old CatalogManager
Branch: master
https://github.com/mongodb/mongo/commit/f2d33bbcde359f5caf2e4e66559dcc46b164cd2b

Comment by Githook User [ 06/Jan/16 ]

Author:

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

Message: SERVER-20037 Clean up calculation of legacy distributed lock process ID
Branch: master
https://github.com/mongodb/mongo/commit/dd0e551071e7128d48d01455e332e30beaa63244

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