Brad Nicholes <[EMAIL PROTECTED]> wrote: > The reason why is because with the introduction of the modular > metric functionality, metric metadata is now passed between gmonds > rather than it being hardcoded into every gmond. In multicast mode, > if you restart the master gmond, it has to request from and wait for > each sub-gmond that is listening on the same multicast channel, to > respond with its metadata for each metric it supports. Depending on > the reporting interval for a collection group, this could take > anywhere from a few seconds to several minutes. In unicast mode the
However, as we discovered a couple of months ago, requesting new metadata doesn't always work as designed, and it can take hours to get everything it needs. Restarting the *other* gmonds in the cluster is sort of a workaround, because each one will send its metadata when it is restarted. This way, you can at least ensure that the least recently restarted gmond knows everything. -- Cos ------------------------------------------------------------------------- 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-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
