[SERVER-77890] Investigate failure to create Database with 'operation was interrupted' error Created: 07/Jun/23 Updated: 07/Jul/23 Resolved: 07/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adi Zaimi | Assignee: | Adi Zaimi |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Operating System: | ALL |
| Participants: |
| Description |
|
As part of the sharded test suite being added for the FCV upgrade/downgrade project, there is a failure to create a database with 'operation was interrupted' error. Looking at the log, it seems we attempt to abort an internal txn when the fcv downgrade command is received, but we can't find the txn in question: has been aborted."... |
| Comments |
| Comment by Adi Zaimi [ 07/Jul/23 ] |
|
We found a workaround in the project to catch this failure in a test script and retry the operation. This works well in that we dont have failures anymore in those tests. Since this is an expected behavior, as Sergi and Paolo suggest, there is nothing more to do for this ticket. |
| Comment by Adi Zaimi [ 07/Jul/23 ] |
|
We found a workaround in the project to catch this failure in a test script and retry the operation. This works well in that we dont have failures anymore in those tests. Since this is an expected behavior, as Sergi and Paolo suggest, there is nothing more to do for this ticket. |
| Comment by Paolo Polato [ 15/Jun/23 ] |
|
Since |