[SERVER-66849] Error labels should account for cluster abort and commit commands Created: 27/May/22 Updated: 29/Oct/23 Resolved: 27/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc8, 6.1.0-rc0 |
| Type: | Bug | 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 | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v6.0
|
||||
| Sprint: | Sharding NYC 2022-05-30 | ||||
| Participants: | |||||
| Description |
|
When the transaction API runs in router mode from a shard, it uses a "cluster" prefix for the commands it runs to distinguish them from the mongod versions. Error label generation uses the command's name to know if it is a commit or abort, but does not account for the "cluster" prefix, so it can return incorrect labels for commands run in this configuration. |
| Comments |
| Comment by Githook User [ 28/May/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 6670518c902d4cef237bb3539da85a75eaa69fe7) |
| Comment by Githook User [ 27/May/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |