[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: |
|
||||||||
| 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: |