[SERVER-76003] Implement cluster parameters consistency check Created: 12/Apr/23 Updated: 24/Jan/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||
| Backport Requested: |
v7.3
|
||||||||||||
| Participants: | |||||||||||||
| Story Points: | 2 | ||||||||||||
| Description |
|
Cluster parameters are persisted by all shards of the cluster and by the config server as well. Specifically, these are stored into the clusterParameters collection of the config database. The goal of this task is to implement a consistency check to verify that the cluster parameter configuration is consistent across all nodes where it is persisted. The check procedure must be synchronized with the setClusterParameter command by locking the _kShardMembershipLock mutex in exclusive mode. Currently the goal is to check the consistency of the persisted configuration on disk. Subsequently it will be evaluated whether and how to extend the check to the one in memory as well. |