[SERVER-40997] Transaction may unexpectedly expire before commit in txn_being_applied_to_secondary_cannot_be_killed.js Created: 03/May/19 Updated: 03/Jul/19 Resolved: 03/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2019-07-15 | ||||
| Participants: | |||||
| Linked BF Score: | 28 | ||||
| Description |
|
txn_being_applied_to_secondary_cannot_be_killed.js tests that the periodic job for aborting transactions running longer than the transactionLifetimeLimitSeconds parameter can't kill a transaction while it's being applied on a secondary. It does so by lowering the lifetime limit to 10 seconds, pausing transaction oplog application on a secondary, committing a cross-shard transaction, then sleeping for 30 seconds to give the periodic job enough time to run. The transaction lifetime parameter is lowered on all nodes, so it's possible the transaction is killed (through the periodic job or the transaction coordinator's deadline) before it can be committed, failing the test. The test should be modified to handle this or at least make it less likely. |
| Comments |
| Comment by Matthew Saltz (Inactive) [ 01/Jul/19 ] |
|
In the test failure the test ran for 25 minutes where it normally only runs in 5 minutes, and I'm seeing high-ish disk utilization there. I don't see any other instances of failure and no other BFGs are marked as duplicates of it, so I'm inclined to just close this as won't fix and mark that ticket as waiting on TIG-407. I can't think of any fix I could do to this that's not just adjusting timeouts, and I don't think that would have fixed this problem anyways. jack.mulrow what do you think? |