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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • 70
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Jordi Serra Torrens
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: