[SERVER-65128] Integrate setClusterParameter with getClusterParameter on replica sets Created: 31/Mar/22  Updated: 29/Oct/23  Resolved: 07/Apr/22

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

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

Backwards Compatibility: Fully Compatible
Sprint: Security 2022-04-18
Participants:

 Description   

SERVER-62261 introduced a new set of cluster server parameter integration tests primarily intended to test that getClusterParameter works as intended for every cluster server parameter added into the server. It has a manual workaround for simulating setClusterParameter by directly performing writes rather than hooking into the command itself.

The simulated functions should be replaced with the real setClusterParameter invocation for replica sets. Once SERVER-63870 lands, this can be done for sharded clusters as well.

Additionally, setClusterParameter should write clusterParameterTime as a timestamp rather than a LogicalTime. LogicalTime serializes into a BSONObj that contains the timestamp nested within the first BSONElement, which causes issues when deserializing it in the ClusterServerParameterOpObserver

Finally, setClusterParameter should be explicitly prohibited from running on any cluster mongod since internal-only commands are used to propagate a parameter after it is set from mongos. It should also be prohibited from running on standalones until SERVER-65249 is completed as part of Milestone 3. 



 Comments   
Comment by Githook User [ 07/Apr/22 ]

Author:

{'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'}

Message: SERVER-65128: Improve integration testing and address bugs in setClusterParameter
Branch: master
https://github.com/mongodb/mongo/commit/df9851154bc9847dc6a736dcdb0e85c2176d0520

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