In internal_transactions_kill_sessions.js, we run some test only commands directly against shards. The test only internal transaction command can trigger the shard to throw TransactionParticipantFailedUnyield, which is expected to be handled by a router. Because this test does not talk through a router, this error is bubbled up to the client - we should allow for this error.
Handle TransactionParticipantFailedUnyield in internal transactions concurrency tests
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: