[SERVER-32682] Allow AutoGet helpers to specify lock timeout Created: 12/Jan/18  Updated: 30/Oct/23  Resolved: 09/Feb/18

Status: Closed
Project: Core Server
Component/s: Concurrency, Storage
Affects Version/s: None
Fix Version/s: 3.7.2

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-33265 reduce test run time for lock_manager... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2018-02-12
Participants:

 Description   

If a lock acquisition times out, the AutoGet constructor will uassert.



 Comments   
Comment by Githook User [ 09/Feb/18 ]

Author:

{'email': 'xiangyu.yao@mongodb.com', 'name': 'Xiangyu Yao', 'username': 'xy24'}

Message: SERVER-32682 Use deadline-oriented mechanism for lock timeout
Branch: master
https://github.com/mongodb/mongo/commit/e28c2f4732e490ed8efa6148d20d889dfd603028

Comment by Githook User [ 09/Feb/18 ]

Author:

{'email': 'xiangyu.yao@mongodb.com', 'name': 'Xiangyu Yao', 'username': 'xy24'}

Message: SERVER-32682 Allow AutoGet helpers to specify lock timeout
Branch: master
https://github.com/mongodb/mongo/commit/b52615ee4e518bcb29bd0601d904fd9e059ce77e

Comment by Githook User [ 09/Feb/18 ]

Author:

{'email': 'xiangyu.yao@mongodb.com', 'name': 'Xiangyu Yao', 'username': 'xy24'}

Message: SERVER-32682 Change GlobalLock timeout type to Milliseconds
Branch: master
https://github.com/mongodb/mongo/commit/9b062114129533e1220dca19085b3a872702a28c

Comment by Eric Milkie [ 12/Jan/18 ]

Luckily, our timeout mechanism for Global lock already works that way, so there should be no problem extending the current timeout design to the AutoGet helpers.

Comment by Spencer Brody (Inactive) [ 12/Jan/18 ]

It should also be possible to specify a timeout of 0, meaning that if there's any contention on the lock the acquisition fails immediately

Generated at Thu Feb 08 04:30:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.