[SERVER-34583] Clean up transaction error codes Created: 19/Apr/18 Updated: 29/Oct/23 Resolved: 26/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2018-05-07 | ||||||||
| Participants: | |||||||||
| Description |
|
When a transaction is aborted implicitly, we currently return different error codes due to different timing. When an operation is running and the transaction gets aborted, we return TransactionAborted, but if the transaction is aborted between operations, the next operation gets NoSuchTransaction. We'd like to unify them to be NoSuchTransaction. This will also be consistent with commands sent after failover, where the new primary expects startTransaction field and returns NoSuchTransaction. |
| Comments |
| Comment by Githook User [ 26/Apr/18 ] |
|
Author: {'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto', 'name': 'Matthew Russotto'}Message: |