[SERVER-67193] Ensure Coordinator Began Resharding Before setFCV in setfcv_reshard_collection.js Created: 10/Jun/22 Updated: 29/Oct/23 Resolved: 18/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.10, 6.0.2, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brett Nawrocki | Assignee: | Abdul Qadeer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-nyc-subteam1, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | Add a sleep at the beginning of ConfigsvrReshardCollectionCommand::typedRun(). |
||||
| Sprint: | Sharding 2022-07-11 | ||||
| Participants: | |||||
| Linked BF Score: | 3 | ||||
| Story Points: | 1 | ||||
| Description |
|
setfcv_reshard_collection.js contains two test cases, one testing lastLTSFCV and another testing latestFCV. The first of these will wait to ensure that the resharding coordinator has started before sending the set FCV command, while the second does not. This means that for the latestFCV case, it's possible that the FCV is set before the resharding operation begins on the config server, therefore causing the resharding operation to miss getting aborted during the upgrade procedure as seen in BF-25353. |
| Comments |
| Comment by Max Hirschhorn [ 01/Sep/22 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: (cherry picked from commit 0d5fd57f9e55915550dd7d13340e2944c169c6e2) |
| Comment by Githook User [ 21/Jul/22 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: |
| Comment by Githook User [ 18/Jul/22 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: |