[SERVER-37209] Allow mongos to retry on view resolution errors in a transaction Created: 19/Sep/18  Updated: 29/Oct/23  Resolved: 04/Oct/18

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

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:
Related
is related to SERVER-35707 Figure out the transaction abort stat... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-09-24, Sharding 2018-10-08
Participants:

 Description   

If mongos attempts to read from a view, the shard will throw an exception that forces mongos to retry the command as an aggregation on the underlying collection. Currently, single replica set transactions abort on any error encountered while processing a command, so reading from a view in sharded transaction will abort the entire transaction. Instead, the shard should not abort on CommandOnShardedViewNotSupportedOnMongod and mongos should be able to update its transaction tracking state to account for this.



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

Author:

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

Message: SERVER-37209 Allow mongos to read from views in a transaction
Branch: master
https://github.com/mongodb/mongo/commit/bf4a5f8242579de57cfeacef57ac9a77e94e80d3

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