Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-48030

Fix deadlock with GetShardMap and old RSM

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.2
    • None
    • None
    • Fully Compatible
    • ALL
    • v5.0, v4.4
    • Sharding 2020-05-18, Sharding 2020-07-13, Sharding 2020-06-01, Sharding 2020-06-15, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-24, Sharding 2020-10-19, Sharding 2020-11-02
    • 24

    Description

      The GetShardMap command is holding the ShardRegistryData _mutex, and trying to obtain the ScanningReplicaSetMonitor::SetState lock via a call to ScanningReplicaSetMonitor::getServerAddress. At the same time replica set monitor is publishing it's onConfirmed set event. It obtains the SetState _mutex, and is trying to obtain the ShardRegistryData _mutex via a call to rebuildShardIfExists.

      Attachments

        Activity

          People

            lamont.nelson@mongodb.com Lamont Nelson
            lamont.nelson@mongodb.com Lamont Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: