Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-1219

LeaderElectionSupport recipe is unnecessarily dispatching the READY_START event even if the ELECTED node stopped/expired simultaneously.

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.3.3
    • Fix Version/s: 3.5.0
    • Component/s: recipes
    • Labels:
      None

      Description

      Let's say node has determined as READY and has dispatched DETERMINE_COMPLETE event, at the same time the ELECTED node got stopped or expired . Still the f/w first dispatches the READY_START event to the node and then checks whether the ELECTED node exists() or not. Here it finds there is no 'Stat' corresponding to ELECTED and will again goes to leader determination phase.

      Problem:
      Unnecessarily the READY_START event is dispatching to the node and says node to be ready with the startup/init, even if there is no ELECTED node.

      Proposal
      Reverse the logic, first check whether ELECTED node exists() or not and then if success f/w can dispatch the READY_START event. Otherwise go to the leader determination phase.

        Attachments

          Activity

            People

            • Assignee:
              rakeshr Rakesh R
              Reporter:
              rakeshr Rakesh R
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: