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

Node can't order after view change and catch up

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Complete
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.6.83
    • Component/s: None
    • Labels:
    • Documentation Impact:
      Unset
    • Sprint:
      Ev-Node 19.02

      Description

      Environment:
      indy-node 1.6.759

      Steps to Reproduce:
      1. Set up the pool.
      2. Run load test with load near to production.
      3. Stop several nodes (Node13 and Node20 for example).
      4. Stop the primary to initiate View Change.
      5. Start stopped nodes (one by one, including primary).
      6. Reduce load rate of script.
      7. Wait for the end of catch up on nodes which were stopped.
      8. Try to write several txns.

      Actual Results:
      Pool can write, but nodes which were stopped don't order txns. The last message with "ordered batch request" was written to logs on view 0:
      2019-01-17 12:58:04,538|INFO|replica.py|Node13:6 ordered batch request, view no 0, ppSeqNo 92, ledger 1001, state root None, txn root None, requests ordered 2, discarded 0

      Expected Results:
      Nodes should order after View Change and Catch Up.

      Logs and metrics: s3://qanodelogs/indy-1876/not_ordering_after_VC_and_catchup_17_01_2019
      To get logs, run following command on log processor machine:
      aws s3 cp --recursive s3://qanodelogs/indy-1876/not_ordering_after_VC_and_catchup_17_01_2019/ /home/ev/logs/qanodelogs/indy-1876/not_ordering_after_VC_and_catchup_17_01_2019/

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              VladimirWork Vladimir Shishkin
              Reporter:
              ozheregelya Olga Zheregelya
              Watchers:
              Alexander Shcherbakov, Olga Zheregelya, Renata Toktar, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: