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

Fix deadlock with GetShardMap and old RSM

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0 Required, 4.4.2
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      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
    • Linked BF Score:
      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

            Assignee:
            lamont.nelson Lamont Nelson
            Reporter:
            lamont.nelson Lamont Nelson
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: