[SERVER-55684] Remove resharding's RecipientStateEnum::kSteadyState state Created: 01/Apr/21 Updated: 29/Oct/23 Resolved: 20/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Jamie Anderson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-autocommits, post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||
| Sprint: | Sharding 2021-05-17, Sharding 2021-05-31 | ||||||||||||
| Participants: | |||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
Prior to Additional note: RecipientStateEnum::kSteadyState has generally been associated with the idea that the recipient shard's copy of the data is consistent but stale. This is mostly true and is specifically untrue in the cases where the recipient shard undergoes replication rollback and relies on idempotency for its copy of the data to become consistent again. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 20/May/21 ] |
|
Author: {'name': 'Jamie Anderson', 'email': 'jamie.anderson@mongodb.com', 'username': 'jandersongo'}Message: (cherry picked from commit bddc8a826383210f0a5d480ba1bb7c3f5e8c7799) |
| Comment by Githook User [ 19/May/21 ] |
|
Author: {'name': 'Jamie Anderson', 'email': 'jamie.anderson@mongodb.com', 'username': 'jandersongo'}Message: |
| Comment by Blake Oler [ 19/Apr/21 ] |
|
Linking this ticket to be done after |