On Tue, Jan 10, 2017 at 4:08 PM, Sam Morrison wrote:
>
> > On 10 Jan 2017, at 11:04 pm, Tomáš Vondra wrote:
> >
> > The version is 3.6.2, but the issue that I believe is relevant is still
> not fixed:
> >
sable, 3.6.5 hasn’t had any problems for us.
Sam
> -Original Message-
> From: Mike Dorman [mailto:mdor...@godaddy.com]
> Sent: Monday, January 09, 2017 6:00 PM
> To: Ricardo Rocha; Sam Morrison
> Cc: OpenStack Operators
> Subject: Re: [Openstack-operators] RabbitMQ 3.6.
Great info, thanks so much for this. We, too, have turned off stats collection
some time ago (and haven’t really missed it.)
Tomáš, what minor version of 3.6 are you using? We would probably go to 3.6.6
if we upgrade.
Thanks again all!
Mike
On 1/9/17, 2:34 AM, "Ricardo Rocha"
Same here, running 3.6.5 for (some) of the rabbit clusters.
It's been stable over the last month (fingers crossed!), though:
* gave up on stats collection (set to 6 which makes it not so useful)
* can still make it very sick with a couple of misconfigured clients
(rabbit_retry_interval=1 and
...@gmail.com]
Sent: Monday, January 09, 2017 3:55 AM
To: Matt Fischer
Cc: OpenStack Operators
Subject: Re: [Openstack-operators] RabbitMQ 3.6.x experience?
We’ve been running 3.6.5 for sometime now and it’s working well.
3.6.1 - 3.6.3 are unusable, we had lots of issues with stats DB
We’ve been running 3.6.5 for sometime now and it’s working well.
3.6.1 - 3.6.3 are unusable, we had lots of issues with stats DB and other
weirdness.
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
MIke,
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