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

Ambiguous behavior after node demotion

    Details

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

      indy-node 1.3.308 (master)

      Description

      Case 1:
      "selected primary for instance 2" are different for different nodes after demotion of primary node

      Steps to Reproduce:
      1. Setup the pool of 7 nodes.
      2. Demote primary node (node 2 in this case).
      => View change happened on the rest nodes. "selected primary Node5 for instance 1" and "selected primary Node5 for instance 2" on all of them. (like in INDY-1112)
      3. Promote demoted node back.

      Actual Result:
      On Node2 "selected primary Node6 for instance 2". It differs from the rest nodes.

      Expected Results:
      Selected primary for instance 2 should be the same on all of nodes.

      Case 2:
      After demote and promote primary (node2) node1 has stopped to writing NYMs. Logs are attached.
      Steps to Reproduce:
      The same as in previous case, but selected primaries are different:

        Attachments

        1. 11111.png
          11111.png
          502 kB
        2. image-2018-02-15-11-26-09-005.png
          image-2018-02-15-11-26-09-005.png
          506 kB
        3. logs_rc.7z
          1.31 MB

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                zhigunenko.dsr NIkita Zhigunenko
                Watchers:
                NIkita Zhigunenko, Sergey Shilov
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: