Thanks Kostas and Jonathan for your suggestions.
I spent a quite a few hours on this and in the end decided that the
gmetad was working as designed and that adding a specific timeout on a
socket connection wasn't needed.
This is because the kernel already times out socket connections that
fail, o
On Fri, Jan 25, 2013 at 12:45:10PM +, Nicholas Satterly wrote:
> Does anyone have any ideas of how the connection could at least be
> timed out? Keep in mind that the gmetad is multi-threaded so I'm
> pretty sure that rules out the use of SIGALRM.
..,
> How could a 2 second timeout be enforced
.net
Subject: [Ganglia-developers] Ganglia gmetad thread stuck at TCP SYN SENT
Hi,
We have a situation here where developers deploy a new version of their app in
EC2 by spinning up instances running the new version, adding them to the
auto-scaling group and once all looks good just terminating
Hi,
We have a situation here where developers deploy a new version of
their app in EC2 by spinning up instances running the new version,
adding them to the auto-scaling group and once all looks good just
terminating the instances with the old app version.
Works great for them, however the ganglia
