lester- i'm writing the core of ganglia 3 right now which will address this problem. one of the biggest shortcoming of ganglia 2x was how metrics are multicast. it's very efficient but as you mention.. doesn't handle mixed environments as well as it should.
ganglia 3 will work in hetergeneous environments without the mistranslation of metric keys that you find now. -matt Dec 17, Lester Vecsey wrote forth saying... > Looking through the key_metrics.h file it seems that linux machines get a > different set of keys from aix, and so on. Theres a basic core set of keys > that are on all platforms, but then when it gets to things like pkts_in its > only available for linux. > > In particular pkts_in is key 31, and here is the question: Imagine you have > a gmond running on aix that is getting its xml tcp port queried from a > gmetad, and you add a couple gmonds on linux machines to the same cluster. > The pkts_in keys from the linux machines aren't going to be accepted by the > aix gmond because they key is out of range. > > This begs the question of what a future windows version should do as well -- > should key 31 be considered pkts_in for all platforms, i.e., go by the linux > definitions? I think solaris overlaps, and this is a potential problem as > well. Is ganglia leading towards having metric key definitaions that will be > interchangeable between platforms in a global sense, or perhaps having a > 'platform' key that allows gmond to go by its own set of key listings per > platform type that is sending to it? > > I hope this makes sense.. would appreciate some feedback. > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Ganglia-general mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ganglia-general >
