Have some problem with queue synchronization. Seems to happen if the master node runs out of RAM during synchronization. Then the syncing can't be cancled, and restarting the second node does nothing, the policy can't be removed and nothing can be consumed or published to the queue. Included some screenshots, note how large the Erlang mailbox and gen_server2 buffers are for the stuck queues. Is there a way to "unstuck" them, without restarting the whole cluster?
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/jW36EHf1tQE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.