Hi Matthew,
I'll add just 2c:
We've tried to move from repeatable-read to read committed in Neutron
project.
This change actually has caused multiple deadlocks during regular tempest
test run.
That is a known problem (the issue with eventlet and currect mysql client
library),
but anyway, at
Eugene Nikanorov enikano...@mirantis.com wrote:
Hi Matthew,
I'll add just 2c:
We've tried to move from repeatable-read to read committed in Neutron project.
This change actually has caused multiple deadlocks during regular tempest
test run.
That is a known problem (the issue with
On 31 March 2015 at 17:22, Mike Bayer mba...@redhat.com wrote:
Eugene Nikanorov enikano...@mirantis.com wrote:
Hi Matthew,
I'll add just 2c:
We've tried to move from repeatable-read to read committed in Neutron
project.
This change actually has caused multiple deadlocks during
I was surprised recently to discover that MySQL uses repeatable read for
transactions by default. Postgres uses read committed by default, and
SQLite uses serializable. We don't set the isolation level explicitly
anywhere, so our applications are running under different isolation
levels depending
