[openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues
gkotton at vmware.com
Tue May 24 05:54:41 UTC 2016
We have used tooz to enable concurrency. Zookeeper and Redis worked well. I think that it is certainly something that we need to consider. The challenge becomes a deployment.
From: Damon Wang <damon.devops at gmail.com>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org>
Date: Tuesday, May 24, 2016 at 5:58 AM
To: OpenStack List <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues
I want to add an option which handle by another project Tooz.
with redis or some other drivers, it seems pretty a good choice.
2016-05-17 6:53 GMT+08:00 Ilya Chukhnakov <ichukhnakov at mirantis.com<mailto:ichukhnakov at mirantis.com>>:
On 16 May 2016, at 20:01, Michał Dulko <michal.dulko at intel.com<mailto:michal.dulko at intel.com>> wrote:
It's not directly related, but this reminds me of tests done by geguileo
 some time ago that were comparing different methods of preventing DB
race conditions in concurrent environment. Maybe you'll also find them
useful as you'll probably need to do something like conditional update
to increment a revision number.
Thanks for the link. The SQLA revisions are similar to the 'solutions/update_with_where',
but they use the dedicated column for that . And as long as it is properly configured,
it happens 'automagically' (SQLA will take care of adding proper 'where' to 'update').
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStackemail@example.com?subject:unsubscribe>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev