[SERVER-38629] Schedule task on coordinator creation to call cancelIfNotYetStarted on coordinator after transactionLifetimeLimitSeconds Created: 14/Dec/18 Updated: 29/Oct/23 Resolved: 20/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:DistributedCommit | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2018-12-31 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Comments |
| Comment by Githook User [ 20/Dec/18 ] |
|
Author: {'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi'}Message: |
| Comment by Esha Maharishi (Inactive) [ 18/Dec/18 ] |
|
Assigned to myself for this sprint because I realized without this, the sharded fuzzer suites that do stepdowns may time out if 'commitTransaction' is never sent for a transaction and a stepdown occurs on the node coordinating the transaction. |