rawwar opened a new issue, #55753:
URL: https://github.com/apache/airflow/issues/55753
### Apache Airflow version
3.0.6
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
When using CeleryExecutor, when a task gets killed due to OOM, it directly
goes to failed state instead of retrying.
### What you think should happen instead?
If retries are configured, it should go into "up_for_retry" state.
### How to reproduce
from airflow import DAG
from airflow.operators.python import PythonOperator
from datetime import datetime
def func():
a = "asd"
while True:
a += a*100000
with DAG(
dag_id="oom_example",
start_date=datetime(2024, 1, 1),
schedule="@daily",
catchup=False,
doc_md=__doc__,
tags=["oom"],
) as dag:
hello_task = PythonOperator(
task_id="oom_task",
python_callable=func,
)
### Operating System
macos
### Versions of Apache Airflow Providers
_No response_
### Deployment
Astronomer
### Deployment details
I tested this on Astronomer deployment as well as locally with breeze(on
main branch) and was able to replicate this.
breeze command i used - `breeze start-airflow -b postgres -P 17 --executor
CeleryExecutor`
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
