6 Replies Latest reply on Feb 3, 2011 5:49 AM by dherrero

    Which is the best way to monitor nodes?

    dherrero

      Hi.

      I work in a project where our server needs to monitor different groups of nodes. Concretely 3 groups. Each of one contains 5 servers running JBoss 5.1. Currently we are creating a cluster for each group so we are creating three clusters (ClusterPartition). But we only need to detect hosts up/down. We dont need shared caches, sent custom messages, etc. I ve read It isnt a good idea to create more than one cluster. Which way is the best to reach our goal?

        • 1. Which is the best way to monitor nodes?
          wdfink

          Our app also use not sharing internal objects (JBoss cache, persistence ...). Only a few JMS messages to signal configuration change.

          Also we separate in different clusters because of load behaviour.

          But all use the same database or backend systems.

           

          We monitor

          - JVM (only if it is alive)

          - GC logs of each instance

          - JBoss logfile for application and other ERROR messages

           

          So in my point of view more than one cluster is not a problem (if you know why and what you doing ;-) )

          1 of 1 people found this helpful
          • 2. Which is the best way to monitor nodes?
            dherrero

            thanks. the reason why I am using clusters is because the code needed is minimal. I thought about using directly a jgroups channel. i.e, develop a bean to deploy in JBoss microcontainer. This bean would hava channel member. Maybe it could be good solution?

            • 3. Which is the best way to monitor nodes?
              wdfink

              sounds not bad to me.

              The reason for us is mostly the EJB-RMI loadbalancing and failover.

               

              What do you want to share via the channel, it will help to make the picture clear.

              I found that it is not a good idea to transport lots of information accross the nodes.

              For our configuration only a signal is send and other members reload if it is received.

              We use ATM a JMS topic for this.

              It's simple to implement.

              The first implementation via MBean was not transactional and produce some race-conditions ...

              • 4. Which is the best way to monitor nodes?
                dherrero

                I dont want to share nothing. I only want to detect when the node's groups enters or leaves their groups....

                • 5. Which is the best way to monitor nodes?
                  wdfink

                  just monitoring?

                  is separating with a cluster.log not enough?

                  [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.CLUSTERNAME] All Members : 1 ([192.168.200.16:5099])

                   

                  org.jgroups and org.jboss.ha with a separate appender.

                  • 6. Which is the best way to monitor nodes?
                    dherrero

                    Well, not really. I need to perform actions bases on the group's changes so I need a component (channel or whatever) that detects theses changes. Then I need to register a callback from my application components to that monitor component. In this way my application can execute rules based on the node's status