[SERVER-82062] Allow secondaries to automatically refresh sharding metadata Created: 10/Oct/23  Updated: 09/Nov/23  Resolved: 09/Nov/23

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

Type: Improvement Priority: Major - P3
Reporter: Renato Riccio Assignee: Backlog - Catalog and Routing
Resolution: Duplicate Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Catalog and Routing
Participants:

 Description   

Currently secondaries are refreshing sharding metadata only when receiving a query with the sharding version (from mongos or via mirrored reads).

This means that if a secondary that did not receive any query become primary (for example an hidden node that is made primary after a rs config change) will need to full refresh the metadata and therefore possibly heavily impacting the query performance.

Would be nice to force metadata refresh of all secondaries every time there is a metadata change (like is happening on the primary) and not wait for an upcoming queries


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