[SERVER-84359] Avoid updating cluster parameter values twice in auto-bootstrap Created: 20/Dec/23 Updated: 21/Dec/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Romans Kasperovics | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | car-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Catalog and Routing
|
||||
| Participants: | |||||
| Story Points: | 2 | ||||
| Description |
|
Currently, in auto-bootstrap setup, when the config server is co-located with a shard server, SetClusterParameterCoordinator updates cluster parameter value stored in config.clusterParameter collections twice. |