On Sun, Dec 20, 2009 at 10:49, Spike Spiegel <[email protected]> wrote: > On Mon, Dec 14, 2009 at 2:00 AM, Vladimir Vuksan <[email protected]> wrote: >> I think you guys are complicating much :-). Can't you simply have multiple >> gmetads in different sites poll a single gmond. That way if one gmetad fails >> data is still available and updated on the other gmetads. That is what we >> used to do. > > Would you mind explaining me why having multiple gmetads in different > colos pulling form the same gmond is simpler than the infrastructure I
Conceptually, it may be simpler since you the two gmetad instances can be considered 100% independent of each other; they just happen to have the same polling targets. There's not need, under normal circumstances, for the two installs to deal with each other. The catch is when there is a failure, and you need to bring back one of the two instances. You trade simplicity in up-front configuration for complexity during the recovery. (Not trying to speak for Vladimir, just tossing in a few comments of my own.) I do not claim that this is the proper solution for all places, but it is *a* solution that is good enough for some. -- Jesse Becker ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
