[rabbitmq-discuss] Monitoring for busy_dist_port
simon at rabbitmq.com
Tue May 21 15:38:32 BST 2013
To add to what Tim said: I've run some tests with busy_dist_port
monitoring patched into RabbitMQ and while I can certainly see
busy_dist_port messages, I haven't been able to demonstrate any
improvement in throughput by tweaking zdbbl until they went away - so I
don't see the point in exposing them.
Out of interest, did you see a performance improvement in Riak after
modifying zdbbl, or were you just trying to make the warnings go away? :-)
On 20/05/13 12:15, Iain Hull wrote:
> We are in the process of deploying a Riak cluster, and are wondering if
> some of the lessons we learned monitoring Erlang in Riak should be
> applied to RabbitMQ.
> During testing we noticed a lot of busy_dist_port in the logs, the root
> was cause was a the Erlang kernel parameter zdbbl was set too low. We
> have adjusted the parameter and are now monitoring the logs for
> busy_dist_port errors.
> I have searched the RabbitMQ mailing list for cases of busy_dist_port or
> zdbbl, but cannot find any. I am wondering if RabbitMQ can suffer from
> problems with busy_dist_port or if zdbbl should be set to any particular
> value? Or I should I monitor the RabbitMQ logs for busy_dist_port?
> Iain Hull
> Senior Software Engineer
> iain.hull.workday (Skype)
> iain.hull at workday.com <mailto:iain.hull at workday.com>
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss