[SERVER-37024] On coordinator creation, we should schedule a task to abort the new coordinator after a timeout Created: 06/Sep/18 Updated: 20/Sep/18 Resolved: 20/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | ShardedTxn:DistributedCommit, transaction-coordinator-management | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding 2018-10-08 |
| Participants: |
| Description |
|
The TransactionCoordinatorService should accept a deadline for a newly created coordinator, and upon creation, schedule an asynchronous task to tryAbort when the deadline is hit. |
| Comments |
| Comment by Matthew Saltz (Inactive) [ 20/Sep/18 ] |
|
We no longer need this with new design around poking that puts the commit deadline inside the TransactionCoordinator |