[SERVER-50596] Add kInitializing to RecipientState and kUnused to RecipientState and DonorState for resharding Created: 27/Aug/20  Updated: 29/Oct/23  Resolved: 28/Aug/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: PM-234-M1, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-09-07
Participants:

 Description   

see common_types.idl



 Comments   
Comment by Githook User [ 28/Aug/20 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-50596 Add kInitializing to RecipientState and kUnused to RecipientState and DonorState for resharding
Branch: master
https://github.com/mongodb/mongo/commit/caf0451c59b3a9304743ed82c05d13052600407d

Comment by Haley Connelly [ 27/Aug/20 ]

We're adding kUnused and kInitializing and to both the DonorState and RecipientState for SERVER-49572 - where a new general method in the ReshardingCoordinatorObserver will implement logic for determining when and which promise should be fulfilled.

eg) awaitAllRecipientsCreatedCollection() should be fulfilled once all the RecipientShards go from kUnused->kInitializing.

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