[SERVER-35831] Improve RouterSessionRuntimeState concurrency control Created: 26/Jun/18 Updated: 27/Oct/23 Resolved: 13/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
Currently, instances of this objects are supposed to have ownership attached to a operation context. However, we also hold a shared_ptr around in the TaskExecutor callback. This means that if the operation context gets destroyed, the callback can still be holding the pointer to the runtime state that the original request gave up ownership. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 13/Nov/18 ] |
|
Updating the TransactionRouter now done in the MultiStatementTransactionAsyncRequestsSender (something like that name). |