[SERVER-44591] Unhelpful error message about transactions in a sharded cluster with a standalone shard when trying to use retryable writes Created: 13/Nov/19  Updated: 12/Dec/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3 Desired

Type: Improvement Priority: Major - P3
Reporter: Shane Harvey Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: neweng, sharding-common-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DRIVERS-699 Raise an actionable error message whe... Implementing
is related to PYTHON-2048 Raise an actionable error message whe... Scheduled
Assigned Teams:
Cluster Scalability
Participants:

 Description   

Reported in PYTHON-2048. When a Mongos routes a retryable write to a standalone shard the driver gets the following error:

{
 'n': 0,
 'ok': 1.0,
 'operationTime': Timestamp(1573609811, 1),
 'writeErrors': [{'code': 20,
                  'codeName': 'IllegalOperation',
                  'errmsg': 'Transaction numbers are only allowed on a replica set member or mongos',
                  'index': 0}]
 '$clusterTime': {'clusterTime': Timestamp(1573609811, 1),
                  'signature': {'hash': b'\x00\x00\x00\x00\x00\x00\x00\x00'
                                        b'\x00\x00\x00\x00\x00\x00\x00\x00'
                                        b'\x00\x00\x00\x00',
                                'keyId': 0}}
}

Could we improve this error message?



 Comments   
Comment by Carl Champain (Inactive) [ 13/Nov/19 ]

Hi shane.harvey,

Passing this ticket along to the Sharding team.

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