[SERVER-81062] Update cluster parameter cache on set-/removeQuerySettings and perform single retry on failure Created: 14/Sep/23  Updated: 01/Dec/23  Resolved: 17/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Denis Grebennicov Assignee: Romans Kasperovics
Resolution: Fixed Votes: 0
Labels: M2
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-77463 Implement setQuerySettings command Closed
Fix
Related
related to SERVER-82432 Adjust the 'clusterServerParameterRef... Closed
is related to SERVER-78801 Ensure cluster-wide parameters mechan... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
SERVER-83216 Refactor query settings command imple... Sub-task Closed Romans Kasperovics  
Backwards Compatibility: Fully Compatible
Sprint: QE 2023-10-16, QE 2023-10-30, QE 2023-11-13, QE 2023-11-27
Participants:
Linked BF Score: 35

 Description   

The flow of set-/removeQuerySettings commands (on mongos) need to be modified as follows:

 

We can also clean up the tests, as we will no longer need to update the 'clusterServerParameterRefreshIntervalSecs' parameter.

This also implies that we may remove the 'does_not_support_stepdowns' tag, as the reason it was added is due to setting the 'clusterServerParameterRefreshIntervalSecs' in tests



 Comments   
Comment by Githook User [ 17/Nov/23 ]

Author:

{'name': 'Romans Kasperovics', 'email': 'romans.kasperovics@mongodb.com', 'username': 'romanskas'}

Message: SERVER-81062 Update cluster parameter cache before and after modifications

Cluster parameter values are cached on routers = mongoS and updated (pulled)
from the config-servers periodically by the 'ClusterServerParameterRefresher'
background job. This means, the new cluster parameter value will not be cached
immediately, but after some delay. This delay is problematic for the
'querySettings' cluster parameter which has read-modify-write updates, because
subsequent 'setQuerySettings' or 'removeQuerySettings' commands might have
a non-deterministic outcome. This change minimizes the delay by forcing
'ClusterServerParameterRefresher' iterations before and after the modification.
Branch: master
https://github.com/mongodb/mongo/commit/5fa345a76a56e50d1da4ed43d4c23a13a56d2475

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