[SERVER-3784] Need to add explicit timeout to distributed lock pinger thread Created: 08/Sep/11  Updated: 11/Jul/16  Resolved: 04/Oct/11

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.0.0-rc2
Fix Version/s: 2.0.1, 2.1.0

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

In the lock pinger thread, it's possible for the connection to wait too long for a response from the config server, causing a forfeit of the lock even if this was a temporary network issue. Need to explicitly add a timeout to the connection <= sleepTime.



 Comments   
Comment by auto [ 04/Oct/11 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: add lock pinger conn timeout, to avoid hanging SERVER-3784
Branch: v2.0
https://github.com/mongodb/mongo/commit/59aa78ea649ac467edf9c9cecb8b5a89c3919034

Comment by auto [ 29/Sep/11 ]

Author:

{u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}

Message: add lock pinger conn timeout, to avoid hanging SERVER-3784
Branch: master
https://github.com/mongodb/mongo/commit/e73943d75e9046e4fedb5953ba5a9f749fab8493

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