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

Pool lose quorum after numerous connection problem

    XMLWordPrintable

Details

    • Bug
    • Status: Complete
    • Medium
    • Resolution: Done
    • None
    • None
    • None
    • indy-anoncreds 1.0.32
      indy-node 1.3.324
      indy-plenum 1.2.259
      libindy 1.3.1~406

    • 18.06, 18.07 Stability & Monitoring

    Description

      All cases have been reproduced in Docker with 7 nodes
      X = node3, Y = node6

      Steps to reproduce:
      1. Write some NYMs
      2. Disconnect node which follows the primary instance 2 (nodeY)
      3. Disconnect current primary (nodeX)
      4. Try to write some NYMs
      5. Connect nodeY back
      6. Connect nodeX back

      Expected results:

      • nodeY returned back to pool successfully
      • viewChange completed successfully when (n-f+1) node returned back
      • nodeX returned back to pool successfully

      Actual results:

      • pool lost its quorum and cannot restore it
      • all nodes (exclude X and Y) assume that X and Y are malicious
      • nodeX cannot connect to all the others

      Attachments

        1. 1210-2.7z
          1.11 MB
        2. disc-2.7z
          325 kB
        3. suppressor.sh
          0.4 kB
        4. suppressor.sh
          0.2 kB

        Issue Links

          Activity

            People

              anikitinDSR Andrew Nikitin
              zhigunenko.dsr NIkita Zhigunenko
              Andrew Nikitin, NIkita Zhigunenko
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: