Federico Sacerdoti wrote:
On Monday, November 11, 2002, at 06:23 PM, Steven Wagner wrote:
[been waiting to spring that one :) ]
So it looks like gappy graphs are back on my large cluster data source
(which is actually now three or four hosts instead of just the one).
I haven't checked gmetad lately but does anyone know if it
round-robins the query hosts or is it just building a list and going
top-to-bottom on each pass until it gets a response? Is there a
timeout period involved?
Gmetad's data threads will suck down the XML, process it, then wait a
random interval between 10 and 20 seconds. The "heartbeat" for the RRDS
is 30sec. This means if the interval between two updates is greater than
30sec, the graph data point is "unknown". So there is always at least 10
sec left for the XML processing, which is generally more than enough. In
2.5.2 (?) I am planning to make this interval settable in the config file.
The code for this is in the last 20 lines of data_thread.c
Well, oddly enough the gappy behavior has stopped. The only difference I
can see between today and yesterday is that there are two or three fewer
hosts up (percentage-wise, this is not significant).
Perhaps I reached some sort of "magic number" ...
I'll keep an eye on it, I suppose...
Thanks Fed. :)
