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

Make tests that run removeShard in assert.soon to wait for the state to become "completed" not error on ShardNotFound

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Sharding 2020-12-28
    • Linked BF Score:
      50

      Description

      If the config server primary steps down right after removing the config.shards doc for the shard but before responding with "state": "completed", the mongos would retry the _configsvrRemoveShard command against the new config server primary, which would not find the removed shard in its ShardRegistry if it has done a ShardRegistry reload after the config.shards doc for the shard was removed. This would cause the command to fail with ShardNotFound.

        Attachments

          Activity

            People

            Assignee:
            cheahuychou.mao Cheahuychou Mao
            Reporter:
            cheahuychou.mao Cheahuychou Mao
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: