[SERVER-59803] Set maxTimeMs for catalog cache refresh aggregation Created: 06/Sep/21  Updated: 29/Oct/23  Resolved: 06/Sep/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.4, 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
is caused by SERVER-54874 Ensure reading of consistent config.c... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-09-20
Participants:

 Description   

Since the catalog cache refresh was changed to use an aggregation pipeline instead of a find on config.chunks, now the findChunksOnConfigTimeoutMS server parameter is no longer honored.
This ticket is to restore that behavior so that the catalog cache aggregation has maxTimeMs set to findChunksOnConfigTimeoutMs



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 20/Sep/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-59803 Set maxTimeMs for catalog cache refresh aggregation

(cherry picked from commit 71bcac7695c5520e6d2d1ec7a9e11e98d58813f5)
Branch: v5.0
https://github.com/mongodb/mongo/commit/01fc4bc95e3105c7217573c076ebd40c19317794

Comment by Githook User [ 06/Sep/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-59803 Set maxTimeMs for catalog cache refresh aggregation
Branch: master
https://github.com/mongodb/mongo/commit/71bcac7695c5520e6d2d1ec7a9e11e98d58813f5

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