seanmuth commented on issue #39717:
URL: https://github.com/apache/airflow/issues/39717#issuecomment-2142765432
Seeing this issue on 2.9.1 as well, also only with sensors.
We've found that the DAG is timing out trying to fill up the Dagbag on the
worker. Even with debug logs enabled I don't have a hint about where in the
import it's hanging.
```
[2024-05-31 18:00:01,335: INFO/ForkPoolWorker-63] Filling up the DagBag from
<redacted dag file path>
[2024-05-31 18:00:01,350: DEBUG/ForkPoolWorker-63] Importing <redacted dag
file path>
[2024-05-31 18:00:31,415: ERROR/ForkPoolWorker-63] Process timed out, PID:
314
```
On the scheduler the DAG imports in less than a second.
and not all the tasks from this DAG fail to import, many import just fine,
at the same time on the same celery worker. below is the same dag file as
above, importing fine:
```
[2024-05-31 18:01:52,911: INFO/ForkPoolWorker-3] Filling up the DagBag from
<redacted dag file path>
[2024-05-31 18:01:52,913: DEBUG/ForkPoolWorker-3] Importing <redacted dag
file path>
[2024-05-31 18:01:54,232: WARNING/ForkPoolWorker-3]
/usr/local/lib/python3.11/site-packages/airflow/models/baseoperator.py:484:
RemovedInAirflow3Warning: The 'task_concurrency' parameter is deprecated.
Please use 'max_active_tis_per_dag'.
result = func(self, **kwargs, default_args=default_args)
[2024-05-31 18:01:54,272: DEBUG/ForkPoolWorker-3] Loaded DAG <DAG: redacted
dag>
```
one caveat/note is that it looks like the 2nd run/retry of each sensor is
what runs just fine.
We've also confirmed this behavior was not present on Airflow 2.7.3, and
only started occurring since upgrading to 2.9.1.
--
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]
