It is however interesting that both "lock wait timeouts" and "missing savepoint" errors occur in operations pertaining the same table - securitygroups in this case. I wonder if the switch to pymysl has not actually uncovered some other bug in Neutron.
I have no opposition to a revert, but since this will affect most projects, it's probably worth finding some time to investigate what is triggering this failure when sqlalchemy is backed by pymysql before doing that. Salvatore On 12 June 2015 at 03:32, Eugene Nikanorov <enikano...@mirantis.com> wrote: > Hi neutrons, > > I'd like to draw your attention to an issue discovered by rally gate job: > > http://logs.openstack.org/96/190796/4/check/gate-rally-dsvm-neutron-rally/7a18e43/logs/screen-q-svc.txt.gz?level=TRACE > > I don't have bandwidth to take a deep look at it, but first impression is > that it is some issue with nested transaction support either on sqlalchemy > or pymysql side. > Also, besides errors with nested transactions, there are a lot of Lock > wait timeouts. > > I think it makes sense to start with reverting the patch that moves to > pymysql. > > Thanks, > Eugene. > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
