[SERVER-71519] Add support for handling stale exception from mongos with enableFinerGrainedCatalogCacheRefresh Created: 21/Nov/22  Updated: 18/Dec/23

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

Type: New Feature Priority: Major - P3
Reporter: Randolph Tan Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49701 Make enableFinerGrainedCatalogCacheRe... Blocked
depends on SERVER-78495 Throw out vestiges of enableFinerGrai... In Code Review
Related
is related to SERVER-68686 Add new $_internalOwningShard agg exp... Closed
Assigned Teams:
Catalog and Routing
Sprint: Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2023-01-23
Participants:

 Description   

$_internalOwningShard will add a shard version parameter and checking (separate from the top level command field). To allow running this expression correctly in mongos, it will need to be able to throw StaleConfigException correctly with enableFinerGrainedCatalogCacheRefresh set to true. This is because it requires passing in the shardId of the source of the stale error, which in this case is from a mongos.



 Comments   
Comment by Sergi Mateo Bellido [ 25/Jan/23 ]

I tried to enable the fine grained refreshes some time ago but they weren't properly working. I spent some time trying to fix it but I didn't have time to complete it. Marking this task as blocked.

Comment by Randolph Tan [ 21/Nov/22 ]

Note: we currently decided to disallow $_internalOwningShard from running in mongos. This ticket is created to track work needed to make it possible to be run on mongos if we have a use case for it.

Generated at Thu Feb 08 06:19:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.