Brad Nicholes wrote: > I would suggest that you break up your 120 nodes into separate > cluster on different multicast channels. Then you would have a > different data source for each cluster. By putting them all on the > same channel, every gmond agent is required to store all of the > metric data for all 120 nodes. That is a huge waste of memory. I > would suggest breaking them up in to smaller clusters. If that > doesn't work for you, then you might want to move to unicast rather > than multicast. In unicast mode all of your gmond agents talk to one > or more gmond master nodes directly rather than on a channel. Then > each of the master gmond nodes becomes a separate data source. > Search back through the email list archive for similar questions. > Optimal Ganglia architectures have been discussed previously > including multicast vs unicast.
Thanks Brad, will do. Got it working this morning, based on your earlier suggestions. But saving memory is always a good thing, especially in our "cloud" environment. I also saw as many as 20 nodes "drop out" during the day, maybe that was related to memory or just overload on the master. Unicast sounds like the way to go for us. Thanks, randy ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-general mailing list Ganglia-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-general
