-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.4.2
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
v5.0, v4.4
-
Sharding 2020-12-28, Sharding 2021-01-11, Sharding EMEA 2021-06-14
-
140
A recipient can end up being unable to process a range deletion task if:
- The recipient persists a "pending" range deletion doc for a migration.
- The recipient fails over after cloning indexes, but before majority committing that index creation.
- On step up, the index creation gets rolled back.
- The donor marks the recipient's range deletion doc as no longer pending
- The recipient submits the range for deletion from the op observer
- The range deletion infinitely fails because the shard key index doesn't exist.
Until the range deletion task is processed, the recipient will be unable to re-receive a chunk that overlaps the range deletion task's range.
- causes
-
SERVER-60142 Shard can migrate on top of orphans after filtering metadata was cleared
- Closed
- is duplicated by
-
SERVER-55557 Range deletion of aborted migration can fail after a refine shard key
- Closed
- related to
-
SERVER-47025 moveChunk after refine shard key can hang indefinitely due to missing shard key index
- Closed