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

resharding_disallow_drop.js is not waiting for resharding to acquire distLocks before attempting to drop the collection

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0-rc0
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Linked BF Score:
      70

      Description

      The resharding_disallow_drop.js test intends to wait for resharding to first acquire the db and collection distLocks here, and then attempt to drop the collection, which should fail with MaxTimeMSExpired because the distLocks are held by the resharding operation.

      However, the awaitReshardingStarted function does not guarantee that the resharding operation has acquired the distLocks. It only guarantees that the resharding command started.

        Attachments

          Activity

            People

            Assignee:
            jordi.serra-torrens Jordi Serra Torrens
            Reporter:
            jordi.serra-torrens Jordi Serra Torrens
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: