{bb} Cluster-aware processes?
"Kit Gerrits" <[email protected]> Thu, 12 Apr 2007 18:18:31 +0200
| Newsgroups | gmane.network.bb4.general |
|---|---|
| Message-ID | <003c01c77d1e$36677830$0100630a@kagtqp> |
Hello all! I'm currently using BB 1.9 to monitor a fair number of servers. Some of these servers happen form a cluster, where processes move around a lot. If a cluster application switches to another node, the corresponding processes are no longer running on the default host, which causes BB to issue a warning. I'd like to have BB recognise the fact that the cluster has switched and that the processes are no longer required to run on that specific system. For instance: systems foo1 and foo2 host package foo and systems bar1 and bar2 host package bar. (We also have a cluster where hosts foo1, foo2 and foo3 host applications foo and bar on separate hosts) I have found 2 ways of accomplishing this: A/ changing the BB configuration with each cluster switch This would involve replacing the configuration files on the cluster node and HUP'ing / restarting the BB process I would prefer not to do this, because A) this is a HP-UX system and I'm not very familiar with MC/ServiceGuard and B) I don't trust the software supplier to keep his hands off the cluster configuration script, undo-ing my bb hook C) Messing with the cluster configuration may void any warranty on the system. B/ use the hostname variable in the configuration file. The cluster package associates with a specific address which can be found in the 'hosts' file. If the cluster package 'foo' is active on that node, the IP associated with hostname 'foo' is also active on that host. Is is possible to hook processes in the bb-proc file into the 'foo' hostname? Would BB notice the fact that the IP associated with that hostname has been (de)activated and (de)activate monitoring of the related process? Thanks, Kit -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-= To unsubscribe from this list, or to subscribe to the bb-digest list send e-mail to mailto:[email protected] with unsubscribe bb -and/or- subscribe bb-digest in the BODY of the message.