Re: [I] Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally [airflow]

potiuk closed issue #41276: Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally URL: https://github.com/apache/airflow/issues/41276 -- This is an automated message from the Apache Git Service. To respond to the mess

Re: [I] Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally [airflow]

xudalei1977 commented on issue #41276: URL: https://github.com/apache/airflow/issues/41276#issuecomment-2401105937 > Please check this property AIRFLOW__CELERY__OPERATION_TIMEOUT. In our environment we were getting this airflowtasktimeout error. We had to increase the time from 1.0 sec .

Re: [I] Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally [airflow]

vaibhavnsingh commented on issue #41276: URL: https://github.com/apache/airflow/issues/41276#issuecomment-2346751278 + 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

Re: [I] Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally [airflow]

trlopes1974 commented on issue #41276: URL: https://github.com/apache/airflow/issues/41276#issuecomment-2272228174 There is something messed up. Today I had a filesystem sensor that failed by timeout (airflow task) but the celery task was successful ... A terça, 6/08/2024, 20:15,

Re: [I] Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally [airflow]

scaoupgrade commented on issue #41276: URL: https://github.com/apache/airflow/issues/41276#issuecomment-2271973022 > Maybe, it makes some sense as we do not have that setting in the configuration. But, what is bothering me is WHY? why did it timeout after being queued? We have no exhaustion

Re: [I] Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally [airflow]

trlopes1974 commented on issue #41276: URL: https://github.com/apache/airflow/issues/41276#issuecomment-2271569597 Maybe, it makes some sense as we do not have that setting in the configuration. But, what is bothering me is WHY? why did it timeout after being queued? We have no exhaustio

Re: [I] Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally [airflow]

scaoupgrade commented on issue #41276: URL: https://github.com/apache/airflow/issues/41276#issuecomment-2271143465 That 10 minutes gap could be because of this config: https://github.com/apache/airflow/blob/6229c1c98a2a78d00255d6b6c5b70d032cff9b80/airflow/config_templates/config.yml#L2600

[I] Executor reports task instance finished (failed) although the task says it's queued. (Info: None) Was the task killed externally [airflow]

trlopes1974 opened a new issue, #41276: URL: https://github.com/apache/airflow/issues/41276 ### Apache Airflow version Other Airflow 2 version (please specify below) ### If "Other Airflow 2 version" selected, which one? 2.9.2 ### What happened? Case 2 of iss