zmq: Lack of outbound connection re-use limits scalability with neutron
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.messaging |
Fix Released
|
Undecided
|
James Page |
Bug Description
During testing of the zmq driver with OpenStack Juno on a 300 compute node cloud, instance creation often failed due to nova being unable to access the API of neutron during setup. During setup, neutron sends a number of cast/fanout messages to neutron-
The ZMQ driver needs a bit of a re-design to support connection pooling; this might be done by turning the zmq-receiver into a more general broker for both inbound and outbound messaging, allowing a single point for pooling an re-use as required, and offloading massive fanouts from the openstack daemon making the request.
Changed in oslo.messaging: | |
status: | New → Confirmed |
Changed in oslo.messaging: | |
assignee: | nobody → Li Ma (nick-ma-z) |
Changed in oslo.messaging: | |
milestone: | none → 1.11.0 |
status: | Fix Committed → Fix Released |
Nick
I have the start of a patch to support connection sharing and re-use for outbound messaging, as well as better use of zmq contexts for message batching etc...
Its testing OK now - so I'll put it up for review sometime next week.