[SERVER-71117] movePrimary commit overwrites the whole config document Created: 07/Nov/22 Updated: 29/Oct/23 Resolved: 07/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding EMEA 2022-11-14 |
| Participants: |
| Description |
|
When the new primary shard is changed, the entire document in the config.databases collection, implicitly setting the unset fields to their default value, i.e., `partitioned` to `false`. This problem has no practical effect for end users since the `partitioned` filed it not longer used starting from `6.0` branch. However, this field must be properly managed until it is removed. |
| Comments |
| Comment by Githook User [ 07/Nov/22 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |