[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:
Backports
Depends
depends on SERVER-53920 Periodically obtain remainingOperatio... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding 2021-05-17, Sharding 2021-05-31
Participants:
Story Points: 1

 Description   

Prior to SERVER-53920, the resharding coordinator had chosen all of the recipient shards reaching RecipientStateEnum::kSteadyState as a somewhat arbitrary point for the resharding operation before it would inform the donor shards to write the final resharding oplog entry. Now that the resharding coordinator periodically polls the recipient shards to get an estimate of how much time remains before they'd be completely caught up to all of the donor shards, there is no benefit to having this distinction in the recipient shards.

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: SERVER-55684: Remove resharding's RecipientStateEnum::kSteadyState state

(cherry picked from commit bddc8a826383210f0a5d480ba1bb7c3f5e8c7799)
Branch: v5.0
https://github.com/mongodb/mongo/commit/a097b7567e01aade1f82d2e05e148ef4428d6ca5

Comment by Githook User [ 19/May/21 ]

Author:

{'name': 'Jamie Anderson', 'email': 'jamie.anderson@mongodb.com', 'username': 'jandersongo'}

Message: SERVER-55684: Remove resharding's RecipientStateEnum::kSteadyState state
Branch: master
https://github.com/mongodb/mongo/commit/bddc8a826383210f0a5d480ba1bb7c3f5e8c7799

Comment by Blake Oler [ 19/Apr/21 ]

Linking this ticket to be done after SERVER-53920 to avoid rebase conflicts.

Generated at Thu Feb 08 05:37:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.