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.
Vladimir On Sun, 13 Dec 2009, Spike Spiegel wrote: > indeed, os resources usage for caching should be tightly controlled. > RRD does a pretty good job at that, and for example I know people that > use collectd (which supports multiple output streams) and send data > both remotely and keep a local copy with different retention policies > to solve that problem. > >> This would be addressed by the use of SAN - there would only be one RRD >> file, and the gmetad servers would need to be in some agreement so that they >> both don't try to write the same file at the same time. > > sure, but even with a SAN you'd have to add some intelligence to > gmetad, which from my pov is more than half of the work needed to > achieve gmetad reliability and redundancy while keeping it's current > distributed design. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
