Any news here? Per-socket solution is a conservative solution that
makes zeromq driver work for multiple-workers. Neutron-server has
api-worker and rpc-worker. I'm not sure per-driver is applicable. I
will try to figure it out soon.
On Fri, Jan 23, 2015 at 7:53 PM, Oleksii Zamiatin
23.01.15, 13:22, Elena Ezhova ?:
On Fri, Jan 23, 2015 at 1:55 PM, Ilya Pekelny ipeke...@mirantis.com
mailto:ipeke...@mirantis.com wrote:
On Fri, Jan 23, 2015 at 12:46 PM, ozamiatin
ozamia...@mirantis.com mailto:ozamia...@mirantis.com wrote:
IMHO It should be created
Hi,
Working on zmq driver I've noticed that for now zmq.Context is created
per socket which is definitely redundant. That was introduced by the change
https://review.openstack.org/#/c/126914/5/oslo/messaging/_drivers/impl_zmq.py
It makes the correct thing reducing the global context
On Fri, Jan 23, 2015 at 1:55 PM, Ilya Pekelny ipeke...@mirantis.com wrote:
On Fri, Jan 23, 2015 at 12:46 PM, ozamiatin ozamia...@mirantis.com
wrote:
IMHO It should be created once per Reactor/Client or even per driver
instance.
Per driver, sounds good.
Wouldn't this create regression
On Fri, Jan 23, 2015 at 12:46 PM, ozamiatin ozamia...@mirantis.com wrote:
IMHO It should be created once per Reactor/Client or even per driver
instance.
Per driver, sounds good.
By the way (I didn't check it yet with current implementation of the
driver) such approach should break the
