[SERVER-65249] Activate cluster parameters on standalone Created: 05/Apr/22  Updated: 29/Oct/23  Resolved: 27/Jan/23

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

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

Issue Links:
Problem/Incident
causes SERVER-79236 Server cannot start in standalone if ... Closed
Assigned Teams:
Server Security
Backwards Compatibility: Fully Compatible
Sprint: Security 2022-12-12, Security 2022-12-26, Security 2023-01-09, Security 2023-01-23, Security 2023-02-06
Participants:

 Description   

The new auditConfig cluster parameter needs to work on standalone. We will enable all cluster parameters on standalone. We don't foresee that current cluster parameters will have any issue with this.



 Comments   
Comment by Githook User [ 26/Jan/23 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-65249 Enable cluster parameters on standalone
Branch: master
https://github.com/mongodb/mongo/commit/ddc2bff1fdb83d5d68465cd0dfece6f59d1fbc2f

Comment by Gabriel Marks [ 07/Dec/22 ]

Based on the design for PM-2925, we are not going to add an IDL flag determining whether a cluster parameter is active on standalone mongod. Instead, we are just going to have all cluster parameters be active on standalone. The reasons we believe this to be OK are:
1. Whether or not we are a standalone mongod is a relatively easy condition to check for, and any cluster parameters that should be disabled on standalone can just add this check in their validate function.
2. Only a subset of cluster parameters (specialized cluster parameters) can run custom code upon set, and the extent of what they can do is very limited as they are running within an OpObserver. This means that we don't have to be too worried about what happens if a cluster parameter which is not intended for standalone gets set on standalone – in most cases, they will just be ignored.

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