[SERVER-55685] Remove reshardingFields.abortReason from the config.collections document Created: 01/Apr/21  Updated: 29/Oct/23  Resolved: 12/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: Max Hirschhorn Assignee: Jamie Anderson
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:
Related
related to SERVER-56902 Remove _abortReason member variable f... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-05-03, Sharding 2021-05-17
Participants:
Story Points: 1

 Description   

Participants in a resharding operation do not need to know the specific error from one of the other participants that led the overall resharding operation being aborted. Participants need only the single bit of information communicated via the CoordinatorStateEnum value that the resharding operation is now aborting to trigger their cleanup. The abortReason can therefore be removed from the config.collections entry because it is already present in the config.reshardingOperations collection (also on the config server) so the extra context can be included in the command response.



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

Author:

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

Message: SERVER-55685: Remove reshardingFields.abortReason from the config.collections document
Branch: master
https://github.com/mongodb/mongo/commit/0de67b8e4634af6d614773ec1e55ca8cd5d961f3

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