问题
my application is having deadlock issue where there is a possibility of conflict from three different sides:
1) MySQL database event - that executed every minutes and run couple of update commands in transactions. 2) Background task = that run every seconds and run couple of insert/update commands in transaction.(doctrine) 3) Main FrontEnd API call - based on incoming request, run insert/update commands. Because of high traffic, request density, this is also of high density.(doctrine)
So, what so far I understood by read from internet is that, lowest isolation level 'read uncommitted' will help to perform dirty perform, thus helping minimize deadlocks. But, here in my case, all conflicting operations are UPDATE/INSERT .
Will that isolation level will help here in this case at all??
-- EDIT --
Hello, actually I read that and one of the points there is to use a lower isolation level. However, my main question was about the impact of 'read uncommitted' isolation level to update operation, not asking for a solution on deadlock.
来源：https://stackoverflow.com/questions/19661779/read-uncommitted-isolation-level-impact-on-insert-update-transactions