3 Replies Latest reply on Aug 20, 2004 9:10 AM by sebi presecan

    Tree Cache replecation seems to have some problems

    sebi presecan Newbie

      Hi Guys,

      I´m stressing a little bit a JBOSS 3.2.5 cluster and I encounter some problems with tree cache replication.

      Consider the following scenario:
      - in each the following nodes A, B, C install the tree cache
      - put a value on node A and check it an B & C --- it is working fine
      - unplug the network cable of node B for example
      - wait some minutes
      - plug the node B back to the cluster
      --- and now the strange things starts

      - add a new value on node A ... check the other nodes .... nothing only on node A the value is available ....
      - add a new value on C or B ... the same syntoms ....
      So after an unplug and a plug in ... the tree replication does not work any more....

      I tried also to stop node B instead of plug-out ... in this case is working ...

      For me first scenario is a very possible one, some any help is welcome.

      I´m wondering if this is BUG ... for seems to be ... what do you think?

      Thanks
      Sebi

        • 1. Re: Tree Cache replecation seems to have some problems
          sebi presecan Newbie

          Hi Guys,

          I looked to the code of TreeCache and I resolved some how the problem.
          I hope that someone can explain me the reason of the implementation.

          In startService when the JChannel is initialized the property AUTO_RECONNECT is not set to true.

          Due to this when a cache node is plug-in the viewChange is called only on that node and contains as member only that node. Setting the property on true made the following behaviour: a new view address is assigned to that node and all the cluster nodes are notified that a new node appeared.

          Can some one tell me if there are some good reasons to not set this property?

          Regards
          Sebi

          • 2. Re: Tree Cache replecation seems to have some problems
            Bela Ban Master

             

            "prese" wrote:
            Hi Guys,

            I looked to the code of TreeCache and I resolved some how the problem.
            I hope that someone can explain me the reason of the implementation.

            In startService when the JChannel is initialized the property AUTO_RECONNECT is not set to true.

            Due to this when a cache node is plug-in the viewChange is called only on that node and contains as member only that node. Setting the property on true made the following behaviour: a new view address is assigned to that node and all the cluster nodes are notified that a new node appeared.

            Can some one tell me if there are some good reasons to not set this property?

            Regards
            Sebi




            This is odd; where did you find it (3.2.5) ? Because in CVS head, AUTO_RECONNECT is set to true in ClusterPartition.createService() by default.

            Bela

            • 3. Re: Tree Cache replecation seems to have some problems
              sebi presecan Newbie

              Hi Bela,

              I´m using a 3.2.5 version.

              Thanks
              Sebi