eskarimov commented on issue #19171: URL: https://github.com/apache/airflow/issues/19171#issuecomment-951154393
Hello @luissantanacontato, Could you provide additional info as mentioned [here](https://github.com/apache/airflow/issues/19171#issuecomment-950008224), please? > Hi there - the `AirflowTaskTimeout` is typically raised when a task's execution exceeds its `execution_timeout` which causes it to be stopped by Airflow. > > This parameter is a part of the BaseOperator class and thus applies to all Operators. > > https://github.com/apache/airflow/blob/86a2a19ad2bdc87a9ad14bb7fde9313b2d7489bb/airflow/models/baseoperator.py#L336-L338 > > Have you configured an `execution_timeout` in your task or in your default DAG's `default_args`? I've been looking into the issue today, but couldn't reproduce it. As @SamWheating mentioned, it might be that `execution_timeout` passed as part of default arguments. `EMRContainerOperator` is based upon `BaseOperator`, it support its arguments passed with `kwargs`. Error traceback seems to confirm it, [the error will be raised only when a task instance has non-empty property of `execution_timeout`](https://github.com/apache/airflow/blob/614858fb7d443880451e6111b27fdaf942f563a4/airflow/models/taskinstance.py#L1311) -- 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]
