<div dir="ltr"><div><div>-1 for upgrading it in 6.1. Known devil is better than unknown angel :)<br><br></div>In 7.0 we can try 3.5.0 with updated Erlang.<br><br></div>~thanks<br><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br></div></div></div>
<br><div class="gmail_quote">On Wed, Apr 29, 2015 at 12:20 PM, Davanum Srinivas <span dir="ltr"><<a href="mailto:dsrinivas@mirantis.com" target="_blank">dsrinivas@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Bogdan,<div><br></div><div>Pacemaker, corosync etc, we picked vivid packages right? So don't we test what's in vivid for this too? Apparently it's 3.4.3-2 per [0].</div><div><br></div><div>I agree, we should not do this in 6.1, However, we should start testing this ASAP.</div><div><br></div><div>Another data point, Alexander Nevenchannyy pointed out to me that 3.5.0 came with an updated Erlang that has the following fix:</div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><p>OTP-11497 To prevent a race condition if there is a short communication</p></div><div><p>problem when node-down and node-up events are received. They</p></div><div><p>are now stored and later checked if the node came up just</p></div><div><p>before mnesia flagged the node as down. (Thanks to Jonas Falkevik )</p></div></blockquote><div>
<p>which seems interesting as well.</p><p>thanks,</p><p>dims</p></div><div>[0] <a href="https://launchpad.net/ubuntu/vivid/+package/rabbitmq-server" target="_blank">https://launchpad.net/ubuntu/vivid/+package/rabbitmq-server</a></div><div>[1] <a href="http://www.erlang.org/download/otp_src_17.0.readme" target="_blank">http://www.erlang.org/download/otp_src_17.0.readme</a></div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 29, 2015 at 4:04 AM, Bogdan Dobrelya <span dir="ltr"><<a href="mailto:bdobrelia@mirantis.com" target="_blank">bdobrelia@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello.<br>
<br>
There are several concerns why we have to upgrade RabbitMQ to 3.4.0 [0]:<br>
1) At least two bugfixes related to the current high-load issue with MQ [1]:<br>
- 26404 prevent queue synchronisation from hanging if there is a very<br>
short partition just as it starts (since 3.1.0)<br>
- 26368 prevent autoheal from hanging when loser shuts down before the<br>
winner learns it is the winner (since 3.1.0)<br>
2) We should as well check how the new 'pause-if-all-down' option works<br>
for split brain recovery.<br>
3) We should address the 'force_boot' recommendations from this mail<br>
thread [2] to speed up the MQ cluster assemble time.<br>
<br>
The question is - is it worth it to do this in the 6.1 release scope?<br>
I vote to postpone this for the 7.0 dev cycle as the impact of such<br>
changes might be unpredictable.<br>
<br>
[0] <a href="https://www.rabbitmq.com/release-notes/README-3.4.0.txt" target="_blank">https://www.rabbitmq.com/release-notes/README-3.4.0.txt</a><br>
[1] <a href="https://bugs.launchpad.net/fuel/+bug/1447619" target="_blank">https://bugs.launchpad.net/fuel/+bug/1447619</a><br>
[2]<br>
<a href="http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg51625.html" target="_blank">http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg51625.html</a><br>
<span><font color="#888888"><br>
--<br>
Best regards,<br>
Bogdan Dobrelya,<br>
Skype #<a href="http://bogdando_at_yahoo.com" target="_blank">bogdando_at_yahoo.com</a><br>
Irc #bogdando<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>