> On 08 Dec 2015, at 21:10, Mike Bayer wrote:
>
>
>
> On 12/08/2015 07:28 AM, Renat Akhmerov wrote:
>> Hi,
>>
>> Moshe, thanks a lot for bringing this up. I remember I tried to find a
>> way to change isolation level per connection but also was unable to do that.
>
>
/14/mysql-performance-implications-of-innodb-isolation-modes/
From: gord chung [mailto:g...@live.ca]
Sent: Tuesday, December 08, 2015 2:50 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default
transaction isolation level
we had
Hi,
Moshe, thanks a lot for bringing this up. I remember I tried to find a way to
change isolation level per connection but also was unable to do that.
An advice from oslo team would be very helpful.
Renat Akhmerov
@ Mirantis Inc.
> On 08 Dec 2015, at 13:41, ELISHA, Moshe (Moshe)
>
we had this in ceilometer events. you can see it here:
https://github.com/openstack/ceilometer/commit/898cd3d036c4358aa16f7b3e2028365dc9829213
note, that patch is removing it because it slowed everything way down
because of locking. if you can avoid it, avoid it.
On 08/12/2015 7:28 AM, Renat
Hi Moshe,
Feel free to submit a patch! This seems to be something we want to be
able to configure.
Thanks,
Roman
On Tue, Dec 8, 2015 at 9:41 AM, ELISHA, Moshe (Moshe)
wrote:
> Hi,
>
>
>
> We at Mistral want to move from the default transaction isolation level
On 12/08/2015 07:28 AM, Renat Akhmerov wrote:
> Hi,
>
> Moshe, thanks a lot for bringing this up. I remember I tried to find a
> way to change isolation level per connection but also was unable to do that.
Current SQLAlchemy has a lot of isolation level options.There is a
complete guide to
upfront.
>
>
>
> [1]
> https://www.percona.com/blog/2015/01/14/mysql-performance-implications-of-innodb-isolation-modes/
>
>
>
>
>
>
>
> *From:* gord chung [mailto:g...@live.ca]
> *Sent:* Tuesday, December 08, 2015 2:50 PM
> *To:* openstack-dev@lists.ope
Hi,
We at Mistral want to move from the default transaction isolation level of
REPEATABLE READ to READ COMMITTED as part of a bugfix[1].
I did not find a way to pass the isolation level to sqlachemy using oslo.db and
the current solution is to use monkey-patching[2] that adds the