You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jon Davies (JIRA)" <ji...@apache.org> on 2018/08/28 09:45:00 UTC
[jira] [Commented] (AIRFLOW-2969) Kubernetes executor scheduler
consistently using up CPU
[ https://issues.apache.org/jira/browse/AIRFLOW-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594762#comment-16594762 ]
Jon Davies commented on AIRFLOW-2969:
-------------------------------------
Possibly related: https://issues.apache.org/jira/browse/AIRFLOW-2201
> 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)