[SERVER-56924] Make resharding_abort_command.js test case wait for reshardingFields.recipientShards to exist Created: 13/May/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: | Haley Connelly | Assignee: | Jamie Anderson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| 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-31 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 149 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
Currently, the test expects the recipients to get to steady-state before the abort command is sent. However, it is possible the coordinator document can exist before the reshardingFields.recipientShards have been added when the coordinator transitions to kPreparingToDonate. Thus, the executeAtStartOfReshardingFn in the test case may return early - causing unintended behavior. A potential fix would be to return false if the coordinator exists but the coordinatorDoc.recipientShards do not before attempting to check each recipient shard is in steady-state. |
| 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 c5c6a45a79c88305c37d7b435163940fffed2cc5) |
| Comment by Githook User [ 20/May/21 ] |
|
Author: {'name': 'Jamie Anderson', 'email': 'jamie.anderson@mongodb.com', 'username': 'jandersongo'}Message: |