[SERVER-37347] Differentiate retryable writes from writes in a transaction on mongos Created: 27/Sep/18  Updated: 29/Oct/23  Resolved: 29/Oct/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.5

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: ShardedTxn:RouterSupport
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-11-05
Participants:
Linked BF Score: 0

 Description   

Currently, mongos interprets the presence of a txnNumber in a write request to mean it is a retyable write, and it uses an idempotent retry policy when sending these writes to shards. Now that mongos supports transactions, writes within a transaction will also have a txnNumber, but they are not retryable, so they should use the default no retry policy instead.

This should be done for insert/update/delete and findAndModify.



 Comments   
Comment by Githook User [ 31/Oct/18 ]

Author:

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

Message: SERVER-37347 Add tags to jstest
Branch: master
https://github.com/mongodb/mongo/commit/c80ab84f6cc543071b045415a40b4b66795147c6

Comment by Githook User [ 29/Oct/18 ]

Author:

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

Message: SERVER-37347 Distinguish retryable writes from writes in a transaction on mongos
Branch: master
https://github.com/mongodb/mongo/commit/e4bfad69b838ce75bbe8bd841532d06a6bb32102

Generated at Thu Feb 08 04:45:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.