<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">We’ve been running 3.6.5 for sometime now and it’s working well.<div class=""><br class=""></div><div class="">3.6.1 - 3.6.3 are unusable, we had lots of issues with stats DB and other weirdness. </div><div class=""><br class=""></div><div class="">Our setup is a 3 physical node cluster with around 9k connections, average around the 300 messages/sec delivery. We have the stats sample rate set to default and it is working fine.<br class=""><div class=""><br class=""></div><div class="">Yes we did have to restart the cluster to upgrade.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Sam</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 6 Jan 2017, at 5:26 am, Matt Fischer <<a href="mailto:matt@mattfischer.com" class="">matt@mattfischer.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">MIke,<div class=""><br class=""></div><div class="">I did a bunch of research and experiments on this last fall. We are running Rabbit 3.5.6 on our main cluster and 3.6.5 on our Trove cluster which has significantly less load (and criticality). We were going to upgrade to 3.6.5 everywhere but in the end decided not to, mainly because there was little perceived benefit at the time. Our main issue is unchecked memory growth at random times. I ended up making several config changes to the stats collector and then we also restart it after every deploy and that solved it (so far). </div><div class=""><br class=""></div><div class="">I'd say these were my main reasons for not going to 3.6 for our control nodes:</div><div class=""><ul class=""><li class="">In 3.6.x they re-wrote the stats processor to make it parallel. In every 3.6 release since then, Pivotal has fixed bugs in this code. Then finally they threw up their hands and said "we're going to make a complete rewrite in 3.7/4.x" (you need to look through issues on Github to find this discussion)</li><li class="">Out of the box with the same configs 3.6.5 used more memory than 3.5.6, since this was our main issue, I consider this a negative.</li><li class="">Another issue is the ancient version of erlang we have with Ubuntu Trusty (which we are working on) which made upgrades more complex/impossible depending on the version.</li></ul><div class="">Given those negatives, the main one being that I didn't think there would be too many more fixes to the parallel statsdb collector in 3.6, we decided to stick with 3.5.6. In the end the devil we know is better than the devil we don't and I had no evidence that 3.6.5 would be an improvement.</div></div><div class=""><br class=""></div><div class="">I did decide to leave Trove on 3.6.5 because this would give us some bake-in time if 3.5.x became untenable we'd at least have had it up and running in production and some data on it.</div><div class=""><br class=""></div><div class="">If statsdb is not a concern for you, I think this changes the math and maybe you should use 3.6.x. I would however recommend at least going to 3.5.6, it's been better than 3.3/3.4 was.</div><div class=""><br class=""></div><div class="">No matter what you do definitely read all the release notes. There are some upgrades which require an entire cluster shutdown. The upgrade to 3.5.6 did not require this IIRC.</div><div class=""><br class=""></div><div class="">Here's the hiera for our rabbit settings which I assume you can translate:</div><div class=""><br class=""></div><div class="">rabbitmq::cluster_partition_handling: 'autoheal'<br class=""></div><div class=""><div class="">rabbitmq::config_variables:</div><div class=""> 'vm_memory_high_watermark': '0.6'</div><div class=""> 'collect_statistics_interval': 30000</div><div class="">rabbitmq::config_management_variables:</div><div class=""> 'rates_mode': 'none'</div><div class="">rabbitmq::file_limit: '65535'</div></div><div class=""><br class=""></div><div class="">Finally, if you do upgrade to 3.6.x please report back here with your results at scale!</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Jan 5, 2017 at 8:49 AM, Mike Dorman <span dir="ltr" class=""><<a href="mailto:mdorman@godaddy.com" target="_blank" class="">mdorman@godaddy.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72" class="">
<div class="m_750736985899810261WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt" class="">We are looking at upgrading to the latest RabbitMQ in an effort to ease some cluster failover issues we’ve been seeing. (Currently on 3.4.0)<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt" class="">Anyone been running 3.6.x? And what has been your experience? Any gottchas to watch out for?<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt" class="">Thanks,<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt" class="">Mike<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt" class=""><u class=""></u> <u class=""></u></span></p>
</div>
</div>
<br class="">______________________________<wbr class="">_________________<br class="">
OpenStack-operators mailing list<br class="">
<a href="mailto:OpenStack-operators@lists.openstack.org" class="">OpenStack-operators@lists.<wbr class="">openstack.org</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/<wbr class="">cgi-bin/mailman/listinfo/<wbr class="">openstack-operators</a><br class="">
<br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">OpenStack-operators mailing list<br class=""><a href="mailto:OpenStack-operators@lists.openstack.org" class="">OpenStack-operators@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br class=""></div></blockquote></div><br class=""></div></div></body></html>