Hi. I have been looking through the mailing list for a little bit and finally found some snippets about multicast. I am wondering if there are any large issues in not using multicast, and going with unicast.
My manager is not thrilled and not interested in using or supporting multicast in ganglia, and I am wondering if this is going to cause an issue in using the tool. I have only worked with it in a multicast environment, and never saw an issue, however I don't know what issues there would be in a unicast environment, if that is something that is supported. The snippets I found are: https://sourceforge.net/mailarchive/message.php?msg_id=7047144 i"m sorry but ganglia 2.x relies on multicast for efficient group messaging. we are definitely going to remove the reliance on multicast (only) in the future but i know that doesn"t help you now. https://sourceforge.net/mailarchive/message.php?msg_id=7047148 The more I think about this, the more I"m convinced you are trying to pound a square peg into a round hole. Multicast is an integral part of ganglia. It really sounds to me like you need to run snmpd on each of your machines and just query them from a central collector. You will get the same information you would get with ganglia without the multicast traffic. The big win with ganglia is being able to distribute the data collection and you will lose that if you disable multicast. However, I"ve found that the multicast traffic I see here from monitoring about 250 hosts is nearly unnoticable. I see more broadcast traffic from the few Windows machines we have than from all of the multicast combined. Thanks, Jason
