On Tue, Jul 15, 2008 at 09:39:48PM +0100, [EMAIL PROTECTED] wrote: > Carlo's email from 9 July suggested the opposite - upgrade gmetad first, > the new gmetad would then be able to receive XML from both 3.0 and 3.1 > gmond instances. > > Could someone confirm which (or possibly both) case is recommended > and/or likely to work?
One of the reasons why doing gmetad/frontend first might be better is that since 3.0 the way external metrics (the ones generated with gmetric) is managed in the frontend has changed. If you have gmetric generated metrics in your clusters, when you upgrade to 3.1 in the frontend, you will see them all together with the "core metrics" that come from gmond in an consistent way for all your clusters regardless of which version of gmond are you running on them. If you are using a 3.0 frontend instead, then it will keep all gmetrics in a different page than the core metrics, but only for the clusters that are running 3.0, while lumping all of them together for the ones that are migrated to 3.1 instead which might be confusing and unstable (as it will change as more clusters are migrated from one version to the other). Other than that, as Brad said, the XML interface between gmetad/gmond has been kept backward compatible both ways and therefore it should work either way. Carlo ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
