[SERVER-38459] TransactionRouter shouldn't lose original non internally retryable snapshot and stale version errors Created: 07/Dec/18 Updated: 29/Oct/23 Resolved: 10/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-12-17 |
| Participants: |
| Description |
|
The TransactionRouter re-throws non internally retryable snapshot and stale database/shard version errors in a transaction with the NoSuchTransaction error code for consistency with the other causes of the TransientTransactionError label. This makes debugging failures more difficult however, because the original error is not returned to the client. Instead the final error message should include the original error's context. |
| Comments |
| Comment by Githook User [ 10/Dec/18 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |