[SERVER-63538] Detail how transactions could execute on the merged shard + config server Created: 10/Feb/22  Updated: 06/Dec/22  Resolved: 28/Sep/22

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

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Won't Fix Votes: 0
Labels: sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Participants:
Story Points: 5

 Description   

The transactions code has logic conditioned on being executed on a shard or on a config server. In particular, transaction coordinator may behave differently if executed on Config server.
Investigate if it's necessary to force the transaction coordinator to always pick its role as Config or shard. Investigate if it matters for the mongos sending the transaction. Investigate if a shard coordinator picks a special client to run the local leg of transaction.


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