2 Replies Latest reply on Oct 29, 2015 7:43 PM by xy

    hazelcast2.1.2 bug

    xy

      My english is not very well, I hope you can understand what I say.,thanks!

      i used hazelcast2.1.2 plugin to building a two computer openfire  cluster.。 One computer become seniorClusterMember i called it A. the other one not seniorClusterMember we called B. A and B can communicate with each other. i stop the openfire on  computer A,  In my opinion,B should call the markedAsSeniorClusterMember method of ClusterEventListener , but not。i read the source code of ClusterListener.class, like below:

      1.jpg

      i found !seniorClusterMember=false, so seniorClusterMember's  is true。so the code below  can never be executed.

      2.jpg

        • Re: hazelcast2.1.2 bug
          Tom Evans

          This is an interesting report, thanks for posting.

           

          The Hazelcast clustering model does not really support the concept of a "senior" member, because all the member nodes are considered equal peers in the cluster. Perhaps the simplest thing to do would be to always return "true" - meaning that each member could be marked as senior as soon as it joins the cluster.

           

          However, it would be good to know what the side-effects of this would be. Have you encountered any functional errors or other problems with your cluster caused by the current behavior?