You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "pdebelak (via GitHub)" <gi...@apache.org> on 2023/02/16 17:59:49 UTC

[GitHub] [airflow] pdebelak opened a new issue, #29578: scheduler.tasks.running metric is always 0

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

   ### 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`](https://github.com/apache/airflow/pull/10956/files#diff-bde85feb359b12bdd358aed4106ef4fccbd8fa9915e16b9abb7502912a1c1ab3L1363). 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?
   
   - [X] 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: commits-unsubscribe@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] potiuk closed issue #29578: scheduler.tasks.running metric is always 0

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk closed issue #29578: scheduler.tasks.running metric is always 0
URL: https://github.com/apache/airflow/issues/29578


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] pdebelak commented on issue #29578: scheduler.tasks.running metric is always 0

Posted by "pdebelak (via GitHub)" <gi...@apache.org>.
pdebelak commented on issue #29578:
URL: https://github.com/apache/airflow/issues/29578#issuecomment-1433496018

   It's unclear to me if `self.executor.has_task(task_instance)` is still a valid thing to call to increment this or what the correct way to do this is now.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org