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

One of the nodes does not respond to libindy after several running load test

    Details

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

      indy-node 1.3.51
      libindy 1.3.1~371

    • Epic Link:
    • Sprint:
      Sprint 18.04, Sprint 18.05, 18.06

      Description

      From IS-566:

      In the attached log I see that libindy try to catchup pool transactions from 7 to 25 and one of the nodes (4th) do not response. And there are no logs after it, but libindy should after timeout detect and blacklist not responding nodes and resume catchup from others.

      Logs from Node4: Desktop.7z

        Attachments

        1. Desktop.7z
          4.82 MB
        2. Node1.7z
          4.55 MB
        3. Node1.7z
          4.55 MB
        4. Node10.7z
          4.81 MB
        5. Node11.7z
          4.78 MB
        6. Node12.7z
          4.83 MB
        7. Node13.7z
          5.17 MB
        8. Node14.7z
          4.97 MB
        9. Node15.7z
          4.83 MB
        10. Node16.7z
          4.86 MB
        11. Node17.7z
          4.65 MB
        12. Node18.7z
          5.24 MB
        13. Node19.7z
          4.61 MB
        14. Node2.7z
          4.78 MB
        15. Node20.7z
          4.79 MB
        16. Node21.7z
          4.84 MB
        17. Node22.7z
          4.89 MB
        18. Node23.7z
          4.87 MB
        19. Node24.7z
          5.12 MB
        20. Node25.7z
          4.65 MB
        21. Node3.7z
          4.89 MB
        22. Node4.7z
          4.79 MB
        23. Node5.7z
          4.97 MB
        24. Node6.7z
          4.59 MB
        25. Node7.7z
          9.67 MB
        26. Node8.7z
          5.00 MB
        27. Node9.7z
          9.87 MB

          Issue Links

          relates to

          Task - A task that needs to be done. INDY-1216 [QA] Find out Stability Boundaries (number of clients and nodes for stable work)

          • High - Serious problem that could block progress.
          • Complete

          Bug - A problem which impairs or prevents the functions of the product. IS-600 Load test fails with timeout error

          • High - Serious problem that could block progress.
          • Complete

          Bug - A problem which impairs or prevents the functions of the product. INDY-1238 Node is restarted because of Out of memory error

          • Medium - Has the potential to affect progress.
          • Complete

          Task - A task that needs to be done. INDY-1191 Request view_change_done messages

          • Medium - Has the potential to affect progress.
          • Complete

            Activity

              People

              • Assignee:
                dsurnin Dmitry Surnin
                Reporter:
                ozheregelya Olga Zheregelya
                Watchers:
                Alexander Shcherbakov, Andrew Nikitin, Dmitry Surnin, Olga Zheregelya
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: