[SERVER-85941] Improve discovery of routing information for views Created: 30/Jan/24  Updated: 01/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Mihai Andrei Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-77402 Create ShardRole retry loop utility Backlog
Assigned Teams:
Catalog and Routing
Participants:

 Description   

Suppose there exists a chain of views between 10 and 20 views in length (i.e. view1 is a view on view2 is a view on ... viewN) (as is the case in views_validation.js). In a sharded cluster, an aggregate against such a chain of views may initially fail with a 'StaleConfig' error (but subsequently succeed on a retry) because it will exceed the maximum of 10 StaleConfig retries for each view that it doesn't have routing information for.

This ticket tracks the work to improve this so that such an aggregate does not have to be retried (once such way is to track views in the sharding catalog, another way is for shards to be aware of the views that they own).


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