[SERVER-65661] InternalTransactionReshardingTest and InternalTransactionChunkMigrationTest don't always cause transactions to abort with prepare as configured Created: 14/Apr/22 Updated: 29/Oct/23 Resolved: 14/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc1, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.0
|
||||||||
| Sprint: | Sharding NYC 2022-04-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 63 | ||||||||
| Description |
|
The fixtures currently force a transaction to abort with prepare by configuring the failCommand failpoint to force the prepareTransaction command to fail with NoSuchTransaction on one of the participant shards. However, this doesn't guarantee that the transaction always aborts with prepare since the prepareTransaction commands to the other participant shards could get cancelled if the abort vote is received before the prepareTransaction command requests are sent out. To make the transaction deterministically abort after prepare, the test should instead run a prepareTransaction command against one of the shards directly and run abortTransaction instead. |
| Comments |
| Comment by Githook User [ 15/Apr/22 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: (cherry picked from commit dd0fe8486e5e8a182c53e33aba38bbbad270dea2) |
| Comment by Githook User [ 14/Apr/22 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |