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

Wait for donor shards to have started resharding before asserting that commands are rejected in resharding_prohibited_commands.js

    • Fully Compatible
    • Sharding 2021-03-22, Sharding 2021-04-05
    • 51
    • 1

      In this test, we verify that commands that synchronize with the donor shard in order to know to be rejected (collMod, createIndexes, dropIndexes) are indeed rejected. There exists a window after which the coordinator starts resharding and before the donor shard has reshardingFields in its cached metadata (to reject the command).

      This window itself is fine, because the MODE_S donor resharding lock synchronizes with the MODE_X locks taken for the conflicting commands. So this issue is test behavior only.

      To fix this, the test needs to wait for the donor shard to have written its local metadata document before verifying that commands are blocked.

            Assignee:
            kshitij.gupta@mongodb.com Kshitij Gupta
            Reporter:
            blake.oler@mongodb.com Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: