alippai commented on pull request #15714: URL: https://github.com/apache/airflow/pull/15714#issuecomment-841813128
I agree that this still _is a valid_ solution and opinionated is good (as you know the usage and I don't). The important point is on that I don't know the usage and if I'd have to contribute to the scheduler it could blow into my face (as MySQL is not protecting me, I have to be aware of the different parties doing the exact queries). The change is right, I would just reduce the scope of these "unsafe" regions by starting select transactions only with the READ COMMITED isolation level or putting exclusive write locks into the current ones (which should likely prevent deadlocks if no other party is allowed to use the resource at all). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
