-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTEL Collector exception scheduler termination #42456
Comments
edit edit: I was able to reproduce this. I'll open a PR tomorrow. |
@wolfier @jedcunningham @nathadfield, hi!
as I see from the logs it happens when executor_state==success and ti.state==running is passed there airflow/airflow/jobs/scheduler_job_runner.py Lines 781 to 784 in 1b538a9
searching for the reasons of it in my case is an open question, I think something happens in dead scheduler/executor reincarnation's processes but I guess this should be handled in the code because of failed ti.end_date=None there airflow/airflow/jobs/scheduler_job_runner.py Line 844 in 1b538a9
let me know if I could help more or write a PR |
today caught it again with executor_state==success and ti.state==queued |
Apache Airflow version
Other Airflow 2 version (please specify below)
If "Other Airflow 2 version" selected, which one?
2.10.0
What happened?
An OTEL Collector exception caused the scheduler to terminate unexpectedly.
The exception was due to the processing of an executor event where the tied task instance start_date attribute did not have the expected type of datetime.
What you think should happen instead?
Instead of raising the exception and causing the schedule to terminate, the exception should be caught and an error log to be generated.
How to reproduce
Unknown.
Operating System
n/a
Versions of Apache Airflow Providers
No response
Deployment
Astronomer
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: