potiuk commented on pull request #20894:
URL: https://github.com/apache/airflow/pull/20894#issuecomment-1019549288
> Wow. Not aware of the {"echo": true}. Thanks very much. I will look into
this again
Pretty handy :) . I just learned about it actually while looking at it.
I thought a bit abou this, and I think this might actually be something not
really Airflow-code originated. It really looks like it coudl be caused by
someone running some manual UI operations and not committing it . It feels
strange that Task Instance rows are locked without the DagRun, so it almost
feels like it's either a custom code or manual operations of the users. I spent
quite some time looking at a a potential path where the TI rows could be
locked, but I could not find anything honestly.
So I'd really insist on the users who see it provide us some more details -
particularly what is the "other" query that locks the instances. I think the
code that get's the deadlock is "correct" - it's the "other" code that is at
fault (but we have no idea what the other code is and whether it is a code or
human).
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
