[SERVER-75919] Investigate if runTransactionOnShardingCatalog should always use cluster transaction API Created: 10/Apr/23 Updated: 29/Oct/23 Resolved: 21/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc1 |
| Type: | Task | 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: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||
| Sprint: | Sharding NYC 2023-04-17, Sharding NYC 2023-05-01 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently, runTransactionOnShardingCatalog() will use the clusterRole to decide if the transaction should execute using the local or cluster wide transaction API client. Now that a config server may run shard role operations, we may want the config server to use the remote client for those operations for compatibility. Seemingly all transactions exclusively write to the config server, so this shouldn't impact correctness in the short term, but could be a limitation for future "sharding catalog" transactions. |
| Comments |
| Comment by Githook User [ 01/May/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 041d863e4281a2d64bc384c7586a2ac656f4c453) |
| Comment by Githook User [ 20/Apr/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |