[SERVER-29344] Inform queries on a secondary node when the range deleter starts cleaning-up ranges on the primary Created: 23/May/17  Updated: 05/Oct/23  Resolved: 05/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Nathan Myers Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-31837 Recipient shard should not wait for `... Backlog
Related
related to SERVER-28412 Add flag to allow a query to continue... Closed
Assigned Teams:
Storage Execution
Sprint: Sharding 2017-05-29, Sharding 2017-06-19, Sharding 2017-12-18
Participants:

 Description   

An oplog observer running on shard secondaries watches for writes to collection admin.system.version, document startRangeDeletion.



 Comments   
Comment by Randolph Tan [ 12/Dec/17 ]

Currently blocked because migration commit makes secondaries set the collection to unsharded:

https://github.com/mongodb/mongo/blob/r3.7.0/src/mongo/db/s/collection_sharding_state.cpp#L457-L467

and this effectively make the MetadataManager in secondaries lose track of all the metadata in use by active cursors:

https://github.com/mongodb/mongo/blob/r3.7.0/src/mongo/db/s/metadata_manager.cpp#L180

The work in SERVER-32198 plans to address this issue.

Generated at Thu Feb 08 04:20:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.