Maybe the Quickest worst way to solve it

The executed query is too slow. Get a bigger machine with more cpu/ram/network/resources. measure it. get it down to as small as possible. Ensure it has no downstream procedures, triggers, etc. That's an obvious culprit even if it isn't at this current moment. if it's long break it up into smaller cost queries and execute them getting intermediate results...multi-threaded debugging best practices...

Questions

Honestly it's impossible to know without any debugging info given from the database. I'm sure there's docs online somewhere about that There's really not enough info here, What's your best thought looking at the mysql docs?

Does this process run on multiple machines? Can you list things that you can rule out like out of memory, cpu maxed out, locked tables or locked rows?

Best Answer

I've come to learn from experience that the answer to "why does my code deadlock" is almost always that's the way it was written. In the exceedingling rare off chance that there's a library issue, good chance getting that fixed if you're the only person with the problem. It just won't get prioritized. Unless you submit the fix!