I second my "just use postgress" then - it handles this much better and doesn't
suffer from table lock problems.
(Not _all_ that helpful, sorry)
-ash
> On 4 Jul 2019, at 07:10, Pala Muthiah wrote:
>
> We found at times some read queries lock up the task instance table, piling
> up connections
We found at times some read queries lock up the task instance table, piling
up connections and task heartbeat transactions, which takes longer to
recover. In READ COMMITTED, such long running and full table locks should
be avoided in many cases.
Basically we are trying to improve performance and
Why do you want to change this? Is there something specific you are trying to
achieve with changing this?
(Periodic reminder: I personally recommend people use Postgres - I've always
found it to be more predictable and stable than Mysql)
-ash
> On 3 Jul 2019, at 00:03, Pala Muthiah wrote:
>
Hello everyone
Wanted to find out what is the transaction isolation level used in
airflow's MySQL meta db in your deployments.
Does anybody use READ COMMITTED instead of the default REPEATABLE READ
transaction isolation level of MySQL? Did you observe any issues?
Thanks,
pala
