Ian Cunningham wrote: > Mr. Dibowitz, > > I am unclear as to why you have "all of the boxes...unicast their data > to the ganglia server". Unless you want data being duplicated, this is a > bad idea. I am not sure what you mean by classes or "ganglia setup is a > cluster". I think you should probably set it up with what you call a > class be a cluster instead. You can have multiple clusters under one > gmetad. The gmetad.conf on the 'ganglia server' should look like this IMHO: > data_source "foo" foo1 foo2 > data_source "bar" bar1 bar2
The reason they also unicast to the server is to have a 'catch all' - in the event that a data_source isn't setup for a given class, *every* machine gets kicked with a default to send to the ganglia server, so we have that data. I realize the data is then in two data sources, and that's duplication, but I don't see that as such a big deal. I've tried taking it out but it doesn't change the problem. > It sounds like you want to have clusters of clusters, and to do that you > need to use grids which is a slightly more complicated ball of wax. We have 10 data sources within each cluster - that's it. We also use grids to combine all our clusters, but I've disabled all that since a given cluster doesn't even work. The point is, as I understand it when gmetad is configured as cluster FOO, and gets data for host BAR under data_source BAZ it should write that data to two places: FOO/BAR/ BAZ/BAR/ But it's not, it's only writing it to one. Any ideas? As far as I can tell, I've hit some obscure bug - gmetad has the data, but isn't writing it out... -- Phil Dibowitz P: 310-360-2330 C: 213-923-5115 Unix Admin, Ticketmaster.com "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
