[GitHub] [airflow] potiuk commented on issue #13668: scheduler dies with "MySQLdb._exceptions.OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction')"

[GitBox <gi...@apache.org>]

potiuk commented on issue #13668:
URL: https://github.com/apache/airflow/issues/13668#issuecomment-1327429527

   Well no more details (including server logs showing what deadlocs with what has not been posted here. I asked for it and tit was not provided.
   
   @zsdyx - if you want to speed it up - please provide detailed logs in a readable form:
   
   1) more logs with context of when it happened so that we can see what happened before and after
   2) corrrelated logs from other components from about the time it happened (deadlock is always caused by two parties)
   3) most important - server logs showint the details of what deadlocks with what. Those logs are available only at the server side and you need to ask your db admin (or if you have admin you can do it yourself . Those logs show details - query and client information. We need the logs contining the deadlock los filtered at about the time when it happened
   
   You might also need to enable the feature of logging all deadlocks to the logs
   
   https://dba.stackexchange.com/questions/87350/view-last-several-innodb-deadlocks
   
   If you provide an information, that gives us a chance to help to investigate - if you don't , it does not.
   
   Ideally - you can create github gists with the relevant logs. 
   
   Can we count on your help with that @zsdyx please  ? Otherwise the issue has very little chance for fixing - maybe accidentally.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org