[SERVER-72834] Pave the road for cluster parameters consistency check Created: 13/Jan/23 Updated: 29/Oct/23 Resolved: 12/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-04-17 |
| Participants: |
| Description |
|
Ensure we have all the building blocks in place for 7.0 so that we will be able to backport global consistency check in some later minor release of 7.0. |
| Comments |
| Comment by Antonio Fuschetto [ 12/Apr/23 ] |
|
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. A workable solution could be to have a consistency check to verify that the cluster parameter configuration is consistent across all nodes where it is persisted. SERVER-76003 keeps track of that implementation. |