[SERVER-56774] [Resharding] Clear filtering metadata after dropping the original collection on donor shards post-commit Created: 07/May/21  Updated: 06/Dec/22  Resolved: 10/May/21

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Won't Fix Votes: 0
Labels: PM-234-M3, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-55781 Verify shard version matches before a... Closed
Assigned Teams:
Sharding NYC
Participants:
Story Points: 1

 Description   

Clearing the filtering metadata will prevent concurrent* operations on the same node from completing without refreshing the routing metadata and seeing the latest incarnation of the collection. Clearing the filtering metadata must be "atomic" with the drop.

 

*Concurrent operations will wait behind the critical section, but can possibly slip in right after the collection has been dropped.



 Comments   
Comment by Blake Oler [ 10/May/21 ]

In resharding, new metadata is placed on the config server as part of resharding commit. This means that once Marcos' bugfix as part of SERVER-55781 goes in, this bug won't exist – a second createIndex retry will see the new metadata and fail.

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