[SERVER-9874] Potential deadlock when running connPoolSync Created: 06/Jun/13  Updated: 10/Dec/14  Resolved: 16/May/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.0.9, 2.2.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-6972 C++ driver should use isMaster, not r... Closed
Operating System: ALL
Participants:

 Description   

This was based from a user report at google groups:

https://groups.google.com/forum/?hl=en-US&fromgroups#!topic/mongodb-dev/g1BULoCq1ck

Condition to actually trigger the deadlock (not the just the MutexDebugger warning) is to call connPoolSync when the ReplicaSetMonitor's master node was flagged as not ok.

This is not an issue in the master branch because SERVER-6972 removed the ScopedDbConnection inside ReplicaSetMonitor::_checkStatus.


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