[Openstack] cinder-schduler multi workers

Ivan Kolodyazhny e0ne at e0ne.info
Mon Jun 18 10:03:04 UTC 2018

Hi Jython,

Thank you for pointing attention to it. cinder-scheduler keeps all data in
memory, so we can't just increase workers count to scale it.

Ivan Kolodyazhny,

On Sun, Jun 17, 2018 at 6:44 AM, jython <zijian1012 at 163.com> wrote:

> Here is a patch about "multiple process workers support for
> nova-scheduler" https://review.openstack.org/#/c/159382/
> Before the placement service takes over nova-scheduler, nova-scheduler
> will have problems with thread-safe, inconsistent, etc. therefore, the
> patch was not merged until the implementation of the placement-claims
> mechanism, It was recently merged into the master branch
> https://github.com/openstack/nova/blob/master/nova/cmd/scheduler.py
> So, I think the cinder-scheduler also has this problem.
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20180618/8a3d32ca/attachment.html>

More information about the Openstack mailing list