Potential deadlock when running connPoolSync

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.0.9, 2.2.4
    • Component/s: Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Randolph Tan
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: