[rabbitmq-discuss] Management Plugin stops gathering stats ?

[Rene Parra]

Thanks Simon, I've sent you the logs directly.

I've replicated the problem in our stage environment which has the same
setup.

FYI... we are troubleshooting by removing variables until we can get the
desired behavior.

Any ideas/thoughts would be greatly appreciated.

--rené

On 8/23/11 4:11 AM, "Simon MacMullen" <simon at rabbitmq.com> wrote:

> On 22/08/11 18:31, Rene Parra wrote:
>> Hi everyone...
> 
> Hi Rene!
> 
>> My question is: Is there some upper threshold in the management plugin
>> that I need to set to continue gathering statistics throughout my test ?
>> This feels like a classic ³invisible threshold being hit somewhere² problem.
> 
> No, this should just work. The mgmt plugin should never stop gathering
> statistics. Weird.
> 
>> Would the mgmt-plugin reporting a false stat of ³~0 TPS² result in
>> rabbit ***_not throttling_*** when it exceeds the high watermark for
> memory?
> 
> It shouldn't - mgmt is not involved with throttling, it's just reporting
> what Rabbit is doing. However, the fact that the memory alarm has not
> gone off at this point is also weird, and when two weird things happen
> at once we have to wonder if they're related. They both look related to
> gen_event too. Hmm.
> 
> Do you still have the logs from this run? Could you send them / upload
> them somewhere?
> 
> Cheers, Simon