Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3
    • Fix Version/s: 2.7
    • Component/s: general
    • Labels:

      Description

      If some pre-previous node connects to the local node with the previous node in the message's failed nodes collection additional steps should be done:

      1. Connection with the previous node should be validated.
      2. If a message from the previous node was not received a long time ago, the previous node should be considered as failed and the pre-previous node connection accepted.
      3. If the previous node connection is alive then different scenarios possible
        1. Answer with a new result code causing the pre-previous node to try to reconnect to the previous node
        2. Break connection with the pre-previous node causing to continue the possible cluster split.
        3. Check connections with nodes after pre-previous node and delay decision by answering RES_WAIT to get more predictable split and stable topology.

        Attachments

          Activity

            People

            • Assignee:
              dkarachentsev Dmitry Karachentsev
              Reporter:
              ein Alexandr Kuramshin
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: