seifrajhi commented on issue #41806:
URL: https://github.com/apache/airflow/issues/41806#issuecomment-2518739812
> Just in case anyone else stumbles on this - we hit a very similar issue,
and worked around it by wrapping the dag processor command with `timeout`. So
in our case, where we have a dag-processor per subdir:
>
> ```shell
> timeout --kill-after=10 600 airflow dag-processor --subdir
$AIRFLOW_HOME/dags/$SUB_FOLDER -n 1
> ```
>
> (And then surrounding code/infrastructure will ensure that another
dag-processor is spun up)
Hello @michalc, I am facing the same issue and I am trying to solve it..
using the helm chart, this is snippet of my values file, what should I
change ?
```
dagProcessor:
enabled: true
replicas: 2
revisionHistoryLimit: 5
resources:
requests:
cpu: 2500m
ephemeral-storage: 200Mi
memory: 2500Mi
limits:
ephemeral-storage: 200Mi
memory: 2500Mi
```
--
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]
