[SERVER-38690] Mongos should throw write targeting errors during a transaction Created: 18/Dec/18 Updated: 29/Oct/23 Resolved: 03/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:RouterSupport, todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Sharding 2019-01-14 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Any error encountered in a batch during a transaction is thrown by mongos and mongod (because a transaction cannot succeed if any write fails) leading to a command error instead of individual write errors in the response to the client. However, currently mongos does not throw targeting errors encountered in a transaction batch, leading to a response with a write error instead. For consistency, mongos should throw these errors. |
| Comments |
| Comment by Githook User [ 22/Apr/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 721a6be0ed262112c5af5dd06cf2caa101b2340d) |
| Comment by Githook User [ 22/Apr/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 721a6be0ed262112c5af5dd06cf2caa101b2340d) |
| Comment by Githook User [ 09/Apr/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |
| Comment by Githook User [ 03/Jan/19 ] |
|
Author: {'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}Message: |