[SERVER-49911] Implement drop existing indexes rule for resharding's oplog application Created: 25/Jul/20  Updated: 06/Dec/22  Resolved: 21/Nov/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 0
Labels: PM-234-M4, PM-234-T-oplog-apply
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

For all spellings of dropIndexes oplog entries: Wait for all indexes in the list to become ready if they aren't already ready. Then drop the indexes in the list.

If no ready index compatible with the new shard key pattern remains after dropping the indexes, then

  • Update the config.localReshardingOperations.recipient document to have an error state.
  • Report to the config server that the resharding operation has been aborted.


 Comments   
Comment by Max Hirschhorn [ 21/Nov/20 ]

Recipient shards shouldn't see dropIndexes oplog entries with us doing SERVER-52771 instead. They'll instead be treated as an error as part of SERVER-49909.

Generated at Thu Feb 08 05:21:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.