[rabbitmq-discuss] RabbitMQ crashed in ets:insert_new - looks like a genuine bug...

Eugene Kirpichov ekirpichov at gmail.com
Fri Aug 12 17:02:38 BST 2011

I am not sure that was the case, I think the queue to which node A was
committing was also on node A.

However, the fact that the messages on different nodes happened within
an interval of 2s (which could well be explained by out-of-sync
clocks) hints that perhaps I'm mistaken (maybe this queue was declared
by someone connected to B and ended up on node B, even though I
intended it to be on A) or that there's something else going on.

On Fri, Aug 12, 2011 at 8:55 AM, Matthew Sackman <matthew at rabbitmq.com> wrote:
> On Fri, Aug 12, 2011 at 08:49:34AM -0700, Eugene Kirpichov wrote:
>> The issue is that these errors happened on *different* nodes. Do you
>> think they still should be part of the same story?
> Yup. If a channel on node A is trying to commit to a queue on node B,
> and that queue fails, then certainly the channel on node A can report
> internal errors.
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Eugene Kirpichov
Principal Engineer, Mirantis Inc. http://www.mirantis.com/
Editor, http://fprog.ru/

More information about the rabbitmq-discuss mailing list