We've got about 100 machines running on AWS EC2s, with Ganglia for
monitoring. Because we are on Amazon, we can't use multicast, so the
architecture we have is each cluster has a Bastion machine, and each other
machine in the cluster has gmond send its' data to the bastion, which
gmetad then
Until recently I wasn't controlling the start order of ec2-run-user-data
and ganglia-monitor, so they were starting at the same 'time'. Yesterday I
fixed that, so that now ec2-run-user-data starts at S02 and ganglia-monitor
at S03. I thought the issue might be exactly what you describe -
Hi, Sam -
We've got a similar deployment (EC2 instances unicasting to a per-AZ
gmetad) that we're managing with Puppet, and I can't say we've seen
anything like that.
How are you automating your redeployments and gmond configurations? Could
your gmond instances be starting up before their
3 matches
Mail list logo
