This has happened to me at both places where I've used Ganglia, one running 3.0.7 on RHEL 5 and the other running 3.1.0 on CentOS 4. Occasionally, the graphs for a particular time range (like, say, day) look blocky, as if there isn't enough resolution in the data. It's as if they were being taken from the RRAs for the next-higher time range, but I'm not sure that's what is actually happening.
Usually, only one time range is affected at any given time, and graphs for any other time range look good. Usually, it just goes away after a minute or a few minutes. But then, perhaps another time range starts looking blocky. Anyone else get this? Any ideas about why it is happening? P.S. In case it had to do with trying to view data for a range of time that's just barely longer than what's in the appropriate RRA because maybe gmetad is a second or two behind in putting in the data, I tried an experiment: I changed the $time_ranges array in conf.php, added a -2 to the end of each time range to make it 2 seconds shorter than what should be available in the RRA. Then when that didn't make the problem go away, I tried -1000. But it still happened. -- 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
