[SERVER-62252] Extend ServerParameter class to support cluster-wide server parameters Created: 23/Dec/21  Updated: 06/Dec/22  Resolved: 23/Dec/21

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

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

Issue Links:
Depends
depends on SERVER-62251 Extend ServerParameter class to suppo... Closed
Assigned Teams:
Server Security
Participants:

 Description   

Currently, server parameters are specific to each node. To support PM-2502, the ServerParameter class must be extended to accommodate cluster-wide parameters that will be registered with the yet-to-be-implemented synchronization mechanisms.

  1. Create base validate() function
  2. Define the ServerParameterScope enum type and add a scope member to ServerParameter.
  3. Add generation field that is of type OID and provide getter and setter method for the member.
  4. Split ServerParameterSet::_map into ServerParameterSet::_nodeParameterMap and ServerParameterSet::_clusterParameterMap
  5. Update ServerParameterSet::add(), remove(), getMap(), get() methods to all support both maps.
  6. Update ServerParameter constructor so that the scope can be set during instantiation and to default-initialize the generation to the nil OID.
  7. Enforce that any ServerParameters that are constructed with scope set to cluster are runtime only
  8. Update ServerParameter unit tests as necessary


 Comments   
Comment by Varun Ravichandran [ 23/Dec/21 ]

This ticket was accidentally created when SERVER-62251 was created, so I am closing it and de-linking it from the epic.

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