Alex, They are the only 2 members of the cluster? How about this:
- The gmond.conf on host A is configured unicast and to send data to the *physical* address (not the VIP) of Host B. Do not configure gmond.conf to send data to itself. The only UDP send channel is to host B - Configure the Host B gmond.conf in the above way to send its UDP data from host B to host A, and not to send to itself. - Configure gmetad.conf to poll the floating VIP address of the cluster. Now I have to say I am away from my computers, so this is a thought experiment. But at my previous company we did this for a failover pair of servers that were the headnodes of a larger cluster. It worked OK I think. I also seem to remember that the cygwin gmond behaves a little bit differently to the Linux one in the case where you do/dont want metrics sent to the host itself. Let me know if this helps. :-) regards, Richard Quoting [EMAIL PROTECTED]: >>> Second post today, separate topic... >>> >>> I've got a few machines set up as active/passive clusters running >>> heartbeat/drbd. I am currently monitoring them with ganglia, but I >>> think the information I'm getting leads to a misleading picture. >>> >>> Since both machines are monitored, it looks like I have 8 processors >>> in the cluster (4 each in 2 boxes). But in reality, only 1 of these >>> machines is ever available at 1 time. I am keeping a mental note to >>> myself that any time these clusters are more than 50% utilized, >>> they're really >100% utilized, since the CPUs, RAM, etc from the >>> passive node really shouldn't count in the totals. Always having to >>> drill down to the level of the individual machine to see what's going >>> on is kind of a pain. >>> >>> The only solution I've thought of is to keep gmond turned off on the >>> passive node, and starting it during a resource migration. This would >>> be easy enough, but it would have 2 drawbacks : >>> 1. My stats would say 50% of my cluster is 'down' although it's >>> functioning correctly. >>> 2. It is sometimes useful to monitor stuff on the passive node, and I >>> don't really want to lose that ability. >>> >>> Any better ways to do this? Maybe extend the PHP frontend to be >>> configurable for monitoring active/passive? (Would anyone else have a >>> use for that besides me?) >>> >>> thanks, >>> alex >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> Ganglia-general mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/ganglia-general >>> -- ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
