[DOCS-16257] [SERVER] Investigate changes in SERVER-71627: Refreshed cached collection route info will severely block all client request when a cluster with 1 million chunks Created: 11/Jul/23  Updated: 13/Nov/23  Resolved: 15/Sep/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 4.2.25, 7.0.1, 5.0.21, 4.4.25, 6.0.10, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Joseph Dougherty
Resolution: Fixed Votes: 0
Labels: query, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-71627 Refreshed cached collection route inf... Closed
Participants:
Days since reply: 30 weeks, 1 day ago

 Description   
Original Downstream Change Summary

Expose a new server parameter named routingTableCacheChunkBucketSize. It is available both for mongod and mongos and allow specifying “Size of the routing table cache buckets used to implement chunk grouping optimization”.

Description of Linked Ticket

Refreshing routing info happens under a lot of circumstances on mongos & mongod, e.g. splitting & moving chunks & shard version Check(when routing requests for read/write queries), etc. Efficiency of refreshing is crucial to MongoDB sharded cluster’s core functionalities.
In production clusters, chunk number grows rapidly with data keeps flowing in, resulting longer refreshing duration, all client requests are blocked. Although the sql of client requests is simple and the system load (CPU, MEM, IO) is low, client request jitter time has high latency during the route refreshing. For example, a cluster with 1 million chunks, it’d take seconds to do the refresh, severely blocking all client queries.


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