[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:
Backports
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: SERVER-66849 Error labels should account for cluster abort and commit commands

(cherry picked from commit 6670518c902d4cef237bb3539da85a75eaa69fe7)
Branch: v6.0
https://github.com/mongodb/mongo/commit/233249600339aed492927b8d252f856366a396dc

Comment by Githook User [ 27/May/22 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-66849 Error labels should account for cluster abort and commit commands
Branch: master
https://github.com/mongodb/mongo/commit/6670518c902d4cef237bb3539da85a75eaa69fe7

Generated at Thu Feb 08 06:06:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.