You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Anuj (JIRA)" <ji...@apache.org> on 2019/01/08 10:19:00 UTC

[jira] [Created] (AIRFLOW-3652) KubernetesExecutor not launching worker pods after parallelism threshold is reached

Anuj created AIRFLOW-3652:
-----------------------------

             Summary: KubernetesExecutor not launching worker pods after parallelism threshold is reached
                 Key: AIRFLOW-3652
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3652
             Project: Apache Airflow
          Issue Type: Bug
          Components: executor
    Affects Versions: 1.10.1
            Reporter: Anuj


Kubernetes Executor is not launching any new worker pods once parallelism threshold is reached, even though all other worker pods are completed.

Expected behaviour : KubernetesExecutor should launch pods if the other current pods are no in running state.If number of running pods are equals to parallelism then executor should wait for them to complete before launching new pods.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)