txn_override.js doesn't bump the txnNumber in the log message if it has to retry the transaction multiple times in a row

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding 2018-12-17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Janna Golden
            Reporter:
            Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: