These are transactions done by two different Python processes (nova-api and neutron-server, potentially running on different nodes) talking to two different Galera servers.
1) we do not set transactions isolation level explicitly in OpenStack services - the default is used (which is REPEATABLE READ in MySQL, and we do not change it in our deployments)
2) it's simple SELECT as the transactions in neutron-server is a reader - it does not modify any rows
@Bogdan,
These are transactions done by two different Python processes (nova-api and neutron-server, potentially running on different nodes) talking to two different Galera servers.
1) we do not set transactions isolation level explicitly in OpenStack services - the default is used (which is REPEATABLE READ in MySQL, and we do not change it in our deployments)
2) it's simple SELECT as the transactions in neutron-server is a reader - it does not modify any rows
I believe it's simply a problem with 'casual reads', which we discuss here - http:// lists.openstack .org/pipermail/ openstack- dev/2016- April/093529. html