Loading...

XML

Word

Printable

JSON

Assigned Teams:

Catalog and Routing
Operating System:
ALL
Sprint:
Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11, Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
Linked BF Score:
143

The following scenario can occur:

Migration of a chunk from shard X to shard Y completes with commit/abort and the migration coordinator on shard X persists the decision
Shard X is removed and shut down before the migration coordinator updates config.rangeDeletions on shard Y
Shard Y is left with document in config.rangeDeletions corresponding to that migration with a 'pending: true' flag

The presence of this document will permanently prevent any migrations to shard Y for chunks overlapping this chunk.

In the case where the migration aborted after migrating some documents to shard Y, this will also leave documents in this chunk orphaned on shard Y.

is duplicated by

SERVER-62691 Remove shard does not wait for migrations to finish on the drained shard

is related to

SERVER-61055 Blacklist tests that call removeShard from the check orphans are deleted hook

related to

SERVER-50143 Removing a shard with in-progress transaction coordinators can leave transactions on participants permanently in prepare

SERVER-50146 Removing a shard with 'uncommitted' documents in config.rangeDeletions on migration recipient can lead to incomplete state on donor

SERVER-60767 Ensure that the execution of removeShard() does not interfere with the scheduling/execution of range deletion tasks.