[SERVER-38630] Persist coordinator's deadline along with participant list and apply the deadline when recovering on stepup Created: 14/Dec/18 Updated: 06/Dec/22 Resolved: 08/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | ShardedTxn:DistributedCommit | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Sprint: | Sharding 2019-01-14 |
| Participants: |
| Description |
|
It's just nice to continue to respect the deadline the user specified (through maxTimeMS) on the original request across failover. It could be done pretty easily by just 1) adding a date field to the IDL for the coordinator document 2) writing the date field when the participant list is written 2) reading the date field on stepup and passing it to the coordinator constructor instead of passing transactionLifetimeLimitSeconds (what's currently done) |