[rabbitmq-discuss] Fwd: Excessive memory consumption of one server in cluster setup

[Matthias Reik]

> Pause all publishing before (re)starting any cluster nodes.
Just want to report back that the "work around" did the trick :-) Of course
the situation is not ideal, but we have a working cluster again

Thx Matthias!

Cheers
Matthias

On Mon, Aug 27, 2012 at 10:44 PM, Matthias Reik <matthias.reik at gmail.com>wrote:

> See comments inline
>
> Thanks
> Matthias
>
> On Mon, Aug 27, 2012 at 5:22 PM, Matthias Radestock <matthias at rabbitmq.com
> > wrote:
>
>> Matthias,
>>
>>
>> On 27/08/12 16:02, Matthias Reik wrote:
>>
>>> even though the setup looks slightly differently (since we are not
>>> using the shovel plugin), the reason could be the same. We are
>>> explicitly ACKing the messages (i.e. no auto-ack), even though the
>>> consumers are in the same data-centers (so we should have a reliable
>>> network), but if the acks are lost and that causes memory increase in
>>> the server then it could be the same bug.
>>>
>>
>> As noted in my analysis, the bug has nothing do with the shovel, or
>> consuming/acking - simply publishing to HA queues when (re)starting slaves
>> is sufficient to trigger it.
>
> Wasn't sure I understood it 100% correctly (sorry not too experienced with
> RabbitMQ yet). Thx for the confirmation.
>
>
>>
>>
>>  Is there anything I could do to validate this assumption?
>>>
>>
>> I don't think it's worth the hassle. I am quite certain that you are
>> suffering from the same bug.
>
>  OK, if you expect a fix for the issue to appear soon then I could wait
> with with "fixing" the cluster and try out any updated version. If it will
> take more time, then I will probably go for your (below) suggested
> fix/workaround.
>
>
>>
>>  Is there anything I can do in the meantime to get into a state where I
>>> have a working cluster again
>>>
>>
>> Pause all publishing before (re)starting any cluster nodes.
>>
> Yes, that makes sense.
>
> Thank you for your quick response.
>
>>
>> Regards,
>>
>> Matthias.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120829/80892787/attachment.htm>