[SERVER-2584] clock skew can cause DistributedLock to forcefully taken too early Created: 18/Feb/11  Updated: 12/Jul/16  Resolved: 18/Feb/11

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 1.6.5-post, 1.8.0-rc0

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

Operating System: ALL
Participants:

 Comments   
Comment by auto [ 18/Feb/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: detect clock skew in DistributedLock SERVER-2584
https://github.com/mongodb/mongo/commit/8d4850ae65b5ca314a540090bd94714cf327b71b

Comment by auto [ 18/Feb/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: detect clock skew in DistributedLock SERVER-2584
https://github.com/mongodb/mongo/commit/a1810524d6ecd22250b97369c58a9d2bd090702e

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