[SERVER-65386] Change addShard behavior to keep cluster parameters of the first shard Created: 08/Apr/22 Updated: 29/Oct/23 Resolved: 27/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc3, 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v6.0
|
||||||||||||
| Sprint: | Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
SERVER-63606 introduced serialization between add/remove shard with setClusterParameters, and when adding a shard, it clears the cluster parameters of the replica set, and then send the parameters set in the config server to the shard. This is done to maintain consistency with respect of the parameters throughout the cluster. After some internal discussions, we would like to change the behavior to the following: we should preserve the cluster parameters of the first replica set added into the cluster and overwrite all possible values we have set on the subsequently added shards. |
| Comments |
| Comment by Githook User [ 27/Apr/22 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: (cherry picked from commit c78b6a067da0f6bc123f839f0f62bea64d8adf66) |
| Comment by Githook User [ 27/Apr/22 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |