[SERVER-52838] Clean up resharding state upon seeing a reshardingFields transition to kError on donors/recipients Created: 12/Nov/20  Updated: 29/Oct/23  Resolved: 05/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-error-flow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-54665 Make participants clean up collection... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-05-03, Sharding 2021-05-17
Participants:
Story Points: 2

 Description   

Upon seeing the reshardingFields transition, the shard should write to the coordinator that it has transitioned to error, cancel all requisite operations, then clean up its local metadata.



 Comments   
Comment by Githook User [ 05/May/21 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-52838 Clean up resharding state upon seeing a reshardingFields transition to kError
Branch: master
https://github.com/mongodb/mongo/commit/1b5794b6518b4dba6939c923389f5f1e1358ff8a

Comment by Haley Connelly [ 22/Feb/21 ]

Right now, in resharding_test_fixture, _checkPostState() is only called on success, not error. This ticket should ensure that we check the post state in both cases.

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