[SERVER-54980] Split resharding state documents into mutable and immutable state Created: 05/Mar/21 Updated: 29/Oct/23 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-lifecycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2021-03-22 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
We should also add explicit {strict: true} and {strict: false} labels to all of the resharding structs with a preference for {strict: false} to avoid complications during upgrade/downgrade in the future. |
| Comments |
| Comment by Githook User [ 09/Mar/21 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: Removes the unused strictConsistencyTimestamp field from the recipient Also explicitly sets strict:true and strict:false for all of |