[SERVER-38352] txn_override.js doesn't bump the txnNumber in the log message if it has to retry the transaction multiple times in a row Created: 30/Nov/18 Updated: 29/Oct/23 Resolved: 03/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2018-12-17 |
| Participants: |
| Description |
|
There is a recursive call in retryEntireTransaction in txn_override.js. If we have to retry the transaction there, we pass the old txnNumber, so the log message has the incorrect txnNumber. This can be confusing when debugging because it seems like the txnNumber is never progressing, even though it says the transaction is being retried. Here is an example from a recent BF. |
| Comments |
| Comment by Githook User [ 03/Dec/18 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: |