[rabbitmq-discuss] Request for copies of internal bug reports...

[Matt Wise]

Ideally as much detail as possible. We have a few things that we think
contributed to our RabbitMQ outage the other day, but the changelog entries
are short enough that its not entirely clear whether they were all related
to our issues or not.

We do plan to upgrade soon to 3.2.0, but we have some other work to get
done first. I expect we'll upgrade in the next 4-5 weeks. That being said,
we don't like to upgrade unless we *know* that it will fix things. Often we
get that by reading the actual issues in public bug trackers so that we can
really understand whats going on.

I'd be happy to take this offline too and discuss with you privately if
that would be easier.

Matt Wise
Sr. Systems Architect
Nextdoor.com


On Wed, Nov 6, 2013 at 3:06 AM, Tim Watson <tim at rabbitmq.com> wrote:

> Hi Matt,
>
> How much detail exactly are you looking for? The internal bug tracker is
> private for a reason, but I'm sure we can dig out relevant info for you. If
> this question relates to your other post (about a cluster failure) then
> upgrading to the latest stable version is *always* recommended.
>
> Please bear in mind that upgrading to a different major version can alter
> your database in ways that it is not possible to roll back from, so
> manually backing up your mnesia directories is recommended.
>
> Cheers,
> Tim
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131106/954406f6/attachment.htm>