<div dir="ltr">We run lots of ec2 connections without problem and also use pika 0.9.13 or 0.9.14pre. <div><br></div><div>Some connections go idle for lengthy periods. We use the default heartbeat of 600 secs for most connections.<div>
<br></div><div>If going through a load balancer like EC2's ELB or haproxy, we found a heartbeat of 25 seconds worked well. At the current time we have engineered load balancers out of our architecture by using AWS Route 53 least latency / weighted routing with health checks.</div>
</div><div><br></div><div>Our domain specific framework built on pika automatically reconnects if we do lose a connection, typically trying a different machine in the cluster via the above routing scheme. Inter- and intra-region shovel/federation links do this explicitly using standard multi-endpoint configurations.</div>
<div><br></div><div>So I would try the default of 600 secs, i.e. don't specify a heartbeat, or use 25 secs if a load balancer is in the picture.</div><div><br></div><div>ml</div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Tue, Aug 27, 2013 at 4:21 AM, Michael Klishin <span dir="ltr"><<a href="mailto:mklishin@gopivotal.com" target="_blank">mklishin@gopivotal.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
slash:<br>
<div class="im"><br>
> I tried setting the connection parameter heartbeat_interval to both zero and 3600 and also the socket_timeout to 1860 seconds<br>
<br>
</div>These are pretty high intervals. Have you tried setting heartbeats to, say, 20-30 seconds?<br>
--<br>
MK<br>
<br>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>