[SERVER-75845] Catch InterruptedDueToStorageChange in parallel shell for fcbis_election_during_storage_change.js Created: 07/Apr/23 Updated: 29/Oct/23 Resolved: 19/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Jiawei Yang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2023-04-17, Repl 2023-05-01, Repl 2023-05-15, Repl 2023-05-29, Repl 2023-06-26 | ||||
| Participants: | |||||
| Linked BF Score: | 10 | ||||
| Description |
|
The test expects that the initial sync node intend to vote yes, but not be able to actually record its vote decision when switching out the storage engine. However, we recently added logic to allow retrying the election if the node running for election never learns of the initial syncing node. Once we allow the initial syncing node to continue swapping out the storage engine, we might end up getting an InterruptedDueToStorageChange error here. We should consider catching the InterruptedDueToStorageChange error within the parallel shell, since that would mean the main execution thread successfully progressed. |