-1 for upgrading it in 6.1. Known devil is better than unknown angel :)
In 7.0 we can try 3.5.0 with updated Erlang.
~thanks
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Wed, Apr 29, 2015 at 12:20 PM, Davanum Srinivas dsrini...@mirantis.com
wrote:
Bogdan,
Pacemaker,
I’m -1 for it.
Considering how much time we needed to troubleshoot the problems already, I
don’t think we have time to properly test the upgrade.
On 29 Apr 2015, at 12:37, Sergii Golovatiuk sgolovat...@mirantis.com wrote:
-1 for upgrading it in 6.1. Known devil is better than unknown angel
Alexei,
actually we do not insist this should b done for the MOS 6.1. That was the
question to the audience if someone is having other idea. All these
discussions have roots in the bug
https://bugs.launchpad.net/fuel/+bug/1447619 - we have found the issue with
RabbitMQ cluster behaviour under the
Hello.
There are several concerns why we have to upgrade RabbitMQ to 3.4.0 [0]:
1) At least two bugfixes related to the current high-load issue with MQ [1]:
- 26404 prevent queue synchronisation from hanging if there is a very
short partition just as it starts (since 3.1.0)
- 26368 prevent
I am 100% against the upgrade, folks. We need to ensure that user can use
different network for GRE segmentation for high-load cases and mention this
in Installation and Operations Guides - there is no time for it.
On Wed, Apr 29, 2015 at 2:33 PM, Tomasz Napierala tnapier...@mirantis.com
wrote:
Agree with Vova and Tomasz. It's too late and risky for 6.1, in my opinion.
Best,
-jay
On 04/29/2015 07:55 AM, Vladimir Kuklin wrote:
I am 100% against the upgrade, folks. We need to ensure that user can
use different network for GRE segmentation for high-load cases and
mention this in
