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

Pool can't reach consensus after stopping part of nodes without restart of all nodes

    XMLWordPrintable

Details

    • Bug
    • Status: Complete
    • High
    • Resolution: Done
    • None
    • None
    • None
    • None
    • indy-node 1.2.255

    • INDY 18.01: Stability+, Sprint 18.02 Stability, Sprint 18.03 Stability, DKMS

    Description

      Steps to Reproduce:
      1. Setup pool of 5 node.
      2. Send NYM transaction to check that pool works.
      3. Stop indy-node on node 1.
      4. Send NYM transaction to check that pool still works.
      5. Stop indy-node on node 2.
      6. Send NYM transaction to check that there is no consensus.
      7. Stop indy-node on node 3, send NYM transaction to check that there is no consensus.
      8. One by one start services on nodes 1 - 3 (order doesn't matter), send NYM transaction after each node connection.
      => indy-node is running on each node, but transactions are not written.
      9. Restart indy-node on each node and send NYM transaction.

      Actual Results:
      Pool can reach consensus only after restarting of all nodes.

      Expected Results:
      Pool should reach consensus when n-f nodes are working.

      Additional Information:
      After stopping of 2 nodes instead of 3, all works correctly.
      It doesn't matter, which nodes are stopped. In case of stopping nodes 3 - 5, behavior is the same.

      Attachments

        1. Node1.log
          749 kB
        2. Node2.log
          858 kB
        3. Node3.log
          917 kB
        4. Node4.log
          907 kB
        5. Node5.log
          895 kB
        6. INDY-1081.PNG
          INDY-1081.PNG
          283 kB
        7. INDY-1081_bug.PNG
          INDY-1081_bug.PNG
          89 kB
        8. logs.tar.gz
          1.08 MB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ozheregelya Olga Zheregelya
              Nikita Spivachuk, Olga Zheregelya, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: