Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1298

Fix the issues found in the current logic of catch-up

    Details

    • Type: Bug
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.4
    • Component/s: None
    • Labels:
      None

      Description

      Size: S (PoA)

      In scope of this ticket fix the following issues in the current logic of catch-up:

      • Execution of 3PC-batch after catch-up in case it was applied before catch-up and then reverted at catch-up start.
      • Absence of removal of PrePrepares from Replica.stashingWhileCatchingUp.
      • If catch-up is in progress and some ledger catch-up has not been started yet then the node does not respond older LedgerStatuses for this ledger with ConsistencyProofs until it starts catch-up of this ledger.
      • Different quorums for not newer LedgerStatuses and none-proofs which actually mean the same.
      • Mode.syncing is used instead of Mode.discovering.
      • Wrong log message on reaching the quorum of none-proofs in LedgerManager.canProcessConsistencyProof.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                VladimirWork Vladimir Shishkin
                Reporter:
                spivachuk Nikita Spivachuk
                Watchers:
                Nikita Spivachuk, Vladimir Shishkin
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: