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

Unable to recover write consensus at n-f after f+1 descent

    Details

    • Type: Bug
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Epic Link:
    • Sprint:
      Sprint 18.03 Stability, DKMS

      Description

      Build Info:
      indy-node 1.3.51

      Steps to Reproduce:
      1. Install pool of 6 nodes and send NYM to make sure that pool works.
      2. Stop 6th node >> read NYM >> write NYM.
      3. Stop 5th node >> read NYM >> write NYM.
      4. Stop 4th node >> read NYM >> write NYM.
      5. Stop 3rd node >> read NYM >> write NYM.
      6. Start nodes from 3rd to 6th successively.
      7. Try to write NYM.

      Actual Results:
      Step 7 NYM is not written to ledger so the pool has lost write consensus after descent to f+1 and recovery to >n-f.

      Expected Results:
      Pool should work write NYMs normally after >n-f.

      Workaround:
      Restart the whole pool to write NYMs.

        Attachments

        1. bad_recovery_after_f+1.PNG
          bad_recovery_after_f+1.PNG
          221 kB
        2. INDY-1166.tar.gz
          2.89 MB
        3. INDY-1166-fixed.PNG
          INDY-1166-fixed.PNG
          284 kB

          Issue Links

            Activity

              People

              • Assignee:
                VladimirWork Vladimir Shishkin
                Reporter:
                VladimirWork Vladimir Shishkin
                Watchers:
                Sergey Shilov, Vladimir Shishkin
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: