hadarsharon opened a new issue, #41891:
URL: https://github.com/apache/airflow/issues/41891

   ### Apache Airflow version
   
   2.10.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When running tasks using the `CeleryKubernetesExecutor` on the latest 
Airflow version (2.10.0), a lot of these messages pop up in the Airflow 
Scheduler logs:
   
   ```
   [2024-08-30T13:10:15.553+0000] {scheduler_job_runner.py:1141} ERROR - 
Something went wrong when trying to save task event logs.
   Traceback (most recent call last):
     File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/jobs/scheduler_job_runner.py",
 line 1139, in _run_scheduler_loop
       self._process_task_event_logs(executor._task_event_logs, session)
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^
   AttributeError: 'CeleryKubernetesExecutor' object has no attribute 
'_task_event_logs'
   ```
   
   ### What you think should happen instead?
   
   Prior to upgrading Airflow from 2.9.3 to 2.10.0, this was not an issue. I 
suspect that the introduction of Hybrid Executors, combined with 
CeleryKubernetesExecutor becoming somewhat redundant, is causing this issue. 
   
   I understand that with hybrid executors, this executor is bound to be 
deprecated at some point, but this could be considered a violation of backwards 
compatibility for those who are still using it. 
   
   ### How to reproduce
   
   1. Deploy Airflow 2.10.0 with CeleryKubernetesExecutor
   2. Run a task and observe the scheduler logs
   3. This error should pop up when the scheduler tries to save task event logs
   
   ### Operating System
   
   Debian GNU/Linux 12 (bookworm)
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-amazon==8.27.0
   apache-airflow-providers-atlassian-jira==2.7.0
   apache-airflow-providers-celery==3.8.1
   apache-airflow-providers-cncf-kubernetes==8.3.4
   apache-airflow-providers-common-compat==1.1.0
   apache-airflow-providers-common-io==1.4.0
   apache-airflow-providers-common-sql==1.15.0
   apache-airflow-providers-docker==3.12.3
   apache-airflow-providers-elasticsearch==5.4.2
   apache-airflow-providers-fab==1.2.2
   apache-airflow-providers-ftp==3.10.1
   apache-airflow-providers-google==10.21.1
   apache-airflow-providers-grpc==3.5.2
   apache-airflow-providers-hashicorp==3.7.1
   apache-airflow-providers-http==4.12.0
   apache-airflow-providers-imap==3.6.1
   apache-airflow-providers-jenkins==3.7.0
   apache-airflow-providers-microsoft-azure==10.3.0
   apache-airflow-providers-mysql==5.6.3
   apache-airflow-providers-odbc==4.6.3
   apache-airflow-providers-openlineage==1.10.0
   apache-airflow-providers-postgres==5.11.3
   apache-airflow-providers-redis==3.7.1
   apache-airflow-providers-salesforce==5.8.0
   apache-airflow-providers-sendgrid==3.5.1
   apache-airflow-providers-sftp==4.10.3
   apache-airflow-providers-slack==8.8.0
   apache-airflow-providers-smtp==1.7.1
   apache-airflow-providers-snowflake==5.6.1
   apache-airflow-providers-sqlite==3.8.2
   apache-airflow-providers-ssh==3.12.0
   apache-airflow-providers-tableau==4.6.0
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   Kubernetes deployment on AWS EKS using Airflow Helm Chart 1.15.0 with 
CeleryKubernetesExecutor
   
   ### Anything else?
   
   This happens pretty much every time a task runs as long as you are using the 
CeleryKubernetesExecutor
   
   ### 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]

Reply via email to