-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Closed
Labels
affected_version:2.5Issues Reported for 2.5Issues Reported for 2.5area:Schedulerincluding HA (high availability) schedulerincluding HA (high availability) schedulerarea:corekind:bugThis is a clearly a bugThis is a clearly a bug
Description
Apache Airflow version
2.5.1
What happened
I'd expect the scheduler.tasks.running metric to represent the number of running tasks, but it is always zero. It appears that #10956 broke this when it removed the line that increments num_tasks_in_executor. Right now that variable is set to 0, never incremented, and the emitted as a gauge.
What you think should happen instead
scheduler.tasks.running should either represent the number of tasks running or be removed altogether.
How to reproduce
No response
Operating System
Ubuntu 18.04
Versions of Apache Airflow Providers
No response
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
affected_version:2.5Issues Reported for 2.5Issues Reported for 2.5area:Schedulerincluding HA (high availability) schedulerincluding HA (high availability) schedulerarea:corekind:bugThis is a clearly a bugThis is a clearly a bug