Martin Knoblauch wrote:
--- Jason Faulkner <[EMAIL PROTECTED]> wrote:
I'm curious about how "possible" or difficult it would be to make
gmetad
backwards compatible -- i.e. where I could leave my 2.5.x gmond
installations alone, and install 3.x gmetad on my main server (and be
able to collect stats despite having a heterogeneous 2.5.x and 3.x
environment). This would allow me to (hopefully) live-migrate my
ganglia
install up to the new version.
--
Jason Faulkner
Systems Manager
Broadwick Corporation
(919) 459-2509
Hi Jason,
although we bumped the major number in the 2.5.x -> 3.0 transition, we
took care to not introduce incompatible changes to the core metrics
framework. In short, I see no reason why a 3.0.4 gmetad should not be
able to query 2.5.x gmond data.
It should even be possible to have a 3.0.4 gmond listen to older
gmonds. Of course, you are limited to multicast until you have replaced
all gmonds.
Jan 3 23:12:07 intranet1 ./gmetad[25006]: RRD_update
(/var/lib/ganglia/rrds/Dev Login
Servers/__SummaryInfo__/part_max_used.rrd): illegal attempt to update
using time 1167883927 when last update time is 1167883927 (minimum one
second step)
I've been receiving repeated errors like this attempting to use a 3.0.x
gmetad with a 2.5.7 gmond. The times are synced perfectly to a local NTP
server, so I'm sure that's not the issue.
--
Jason Faulkner
Systems Manager
Broadwick Corporation
(919) 459-2509
[EMAIL PROTECTED]
