[
https://issues.apache.org/jira/browse/AIRFLOW-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Davies updated AIRFLOW-2969:
--------------------------------
Description:
I've deployed Airflow with the Kubernetes executor, and it consistently sits
there using up CPU cycles when completely idle (no DAGs enabled or running):
{code:java}
kubectl top pods -n production-airflow
...
airflow-scheduler-56cc4d7c97-2lszr 776m 113Mi
...
{code}
When I launch a DAG, this shots up to 2 CPUs (max VM CPUs) used but we're not
seeing this behavior on our non-Kubernetes Airflow instances.
was:
I've deployed Airflow with the Kubernetes executor, and it consistently sits
there using up CPU cycles when completely idle (no DAGs enabled or running):
{code:java}
kubectl top pods -n production-airflow
...
airflow-scheduler-56cc4d7c97-2lszr 776m 113Mi
...
{code}
When I launch a DAG, this shots up to 2 CPUs used but we're not seeing this
behavior on our non-Kubernetes Airflow instances.
> Kubernetes executor scheduler consistently using up CPU
> -------------------------------------------------------
>
> Key: AIRFLOW-2969
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2969
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Jon Davies
> Priority: Major
>
> I've deployed Airflow with the Kubernetes executor, and it consistently sits
> there using up CPU cycles when completely idle (no DAGs enabled or running):
> {code:java}
> kubectl top pods -n production-airflow
> ...
> airflow-scheduler-56cc4d7c97-2lszr 776m 113Mi
> ...
> {code}
> When I launch a DAG, this shots up to 2 CPUs (max VM CPUs) used but we're not
> seeing this behavior on our non-Kubernetes Airflow instances.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
