[SERVER-35357] Implement a temporary map of transaction runtime states on MongoS Created: 01/Jun/18 Updated: 29/Oct/23 Resolved: 28/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Randolph Tan |
| 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-06-18, Sharding 2018-07-02, Sharding 2018-07-16 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
In order to be able to make progress on the sharded transactions work before the SessionCatalog is made decorable and made available on mongos, we should just create a simple std::map<LogicalSessionId, TransactionRuntimeState> in order to be able to store per-session transaction information. In order to abstract this temporary map, the API for TransactionRuntimeState should behave like a decoration on OperationContext, even though it might not be one at first. E.g.: static TransactionRuntimeState* TransactionRuntimeState::get(OperationContext* opCtx); Should include some basic unit-tests. |
| Comments |
| Comment by Githook User [ 20/Jun/18 ] |
|
Author: {'username': 'renctan', 'name': 'Randolph Tan', 'email': 'randolph@10gen.com'}Message: |