[rabbitmq-discuss] Stats node getting slow

Mon Nov 11 14:51:30 GMT 2013

Doh, thanks Michael!

This gives me the ability to script everything up so yeah, I am going to
let the dust settle this week and then try to convince the oncall (the
pages for this module go to somebody else at this point so it's not really
my call :) ) to revert to the old config over the weekend and help you guys
out narrowing the issue.

BTW, it could be related or not but since I am at it I thought to report
it: I did some throughput benchmarks a year ago on 3.0.x series trying to
figure what sustained message rates we could get in different replication
configurations. I repeated the experiments recently on 3.1.x and noticed
that the numbers dropped quite a bit. It's difficult to say exactly by how
much because we are serving also live traffic now on the same cluster so
there is less isolation but I would say the throughput dropped by 20/30%. I
wonder if this can also be related to the stats node messing up. Not super
important right now because we ended up using redis for the component that
was generating that high volume since anyway they just needed a lightweight
pub/sub and not really the queueing features that much.

Thanks again for the help and hopefully I'll get back to you with some data
soon.

Best, Pier

On Mon, Nov 11, 2013 at 6:28 AM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On 11 Nov 2013, at 18:24, Pierpaolo Baccichet <pierpaolo at dropbox.com>
> wrote:
>
> >  A related question, is there a way to programmatically figure which one
> is the stats node in the cluster? I could not find the config in the HTTP
> API
>
> GET /api/overview and see "statistics_db_node"
>
> MK
>
> Software Engineer, Pivotal/RabbitMQ
>
>
> _______________________________________________
> 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/20131111/e06953cf/attachment.htm>