openstack team mailing list archive

["Pitucha, Stanislaw Izaak" <stanislaw.pitucha@xxxxxx>]

Hi all,
Could someone explain what's the relation between the internal threading and number of rabbitmq connections that can exist on a single service? (in diablo final)

I'm wondering under what circumstances can I get multiple connections from a single compute or network manager to the rabbitmq server when using kombu library? Can it use any connection pooling mechanism instead? I can see that it's not used by default, since there are multiple connections started from both of those services at the moment.

The source of those questions is a strange thing I noticed where the number of open connections just keeps growing in my cluster, finally hitting open files limit on rabbitmq, ... which is a bad thing of course. From the network dump it seems that most "idle" requests are method:get_instance_nw_info and then service gets the response with addresses, bridges etc. correctly. But each connection like that just stays open for a long time.
It seems that sometimes the number of connection spikes up much more than the average - but I didn't get the occasion to capture it. So far all compute and network services have between 1 and 3 connections open each.

Did someone see this in their own environment and can give more details on this behavior?

Regards,
Stanisław Pitucha
Cloud Services 
Hewlett Packard