Jesse Alvarez <[email protected]> wrote: > If a (source) server listed in the data_source directive becomes > unavailable, the source does not move on to the next available > server(s).
> data_source "App cluster" app001:8600 app100:8600 app200:8600 > - app001 becomes unavailable for some reason. > - Source data should now be pulled from app002, but it does not Can you be more specific about "for some reason"? Also, what do you see in the syslog on the host running gmetad? There's a known problem if the data_source node *does* allow a TCP connection to be successfully made, but gmond does not respond with the data, or times out. In that case, gmetad will take the success of the connection to mean that it succeeded with that data source, and will not try the next one. If, on the other hand, it's not even getting a TCP connection, but still not moving on to the next data_source, you may have found a new problem. Whichever case it is, the error message gmetad logs to syslog (or, perhaps, a complete absence of any error message?) should shed some light on it. -- Cos ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
