[SERVER-20425] Sharding dist lock acquisition must update the latest optime on the catalog manager Created: 15/Sep/15  Updated: 25/Jan/17  Resolved: 18/Sep/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.1.9

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 9 (09/18/15), Sharding A (10/09/15)
Participants:

 Description   

Since the distributed lock manager has its own catalog, lock acquisitions do not cause the latest optime to be updated on the owning catalog manager.



 Comments   
Comment by Githook User [ 18/Sep/15 ]

Author:

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

Message: SERVER-19855 SERVER-20425 Make ShardRegistry responsible for tracking the config server optime.
Branch: master
https://github.com/mongodb/mongo/commit/a3ef7c1a233148861b3c8ada4849f5763d26d5f8

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