tanelk commented on issue #19957:
URL: https://github.com/apache/airflow/issues/19957#issuecomment-1094995228
In yout last log you have:
--
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 specif
tanelk commented on issue #19957:
URL: https://github.com/apache/airflow/issues/19957#issuecomment-1094996707
In your last log you have some long lines, that seem to be truncated. For
example:
`Process 309021: SELECT task_instance.try_number AS
task_instance_try_number, task_instance
tanelk commented on issue #19957:
URL: https://github.com/apache/airflow/issues/19957#issuecomment-1095027253
The python logs allways seem to show the update query in
`dagrun.schedule_tis`. It would be most helpful to see the second half of this
deadlock. In PostgreSQL log there was a hint
tanelk commented on issue #19957:
URL: https://github.com/apache/airflow/issues/19957#issuecomment-1095150968
> > The python logs allways seem to show the update query in
`dagrun.schedule_tis`. It would be most helpful to see the second half of this
deadlock. In PostgreSQL log there was a h
tanelk commented on issue #19957:
URL: https://github.com/apache/airflow/issues/19957#issuecomment-1095211422
The UPDATE statement seems to be constant, but I can't figure out where the
SELECT statement is coming from. SQLAlchemy is probably obfuscating it a bit
also.
--
This is an autom
tanelk commented on issue #19957:
URL: https://github.com/apache/airflow/issues/19957#issuecomment-1095230786
> >
>
> I managed to run a large number tasks without airflow crashing, so
changing that setting as you suggested did indeed help! Thank you! :)
Does this still apply,
tanelk commented on issue #19957:
URL: https://github.com/apache/airflow/issues/19957#issuecomment-1095242676
In prostgre log the block, that starts with `ERROR: deadlock detected`
should tell what queryies are conflicting. There might be other unrelated query
around it - most likely seria
