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

Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/01/21 11:40:00 UTC

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

     [ https://issues.apache.org/jira/browse/AIRFLOW-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ash Berlin-Taylor resolved AIRFLOW-3652.
----------------------------------------
    Resolution: Duplicate

> 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
>            Priority: Major
>
> 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.
> Also if I don't set any parallelism then after certain number of pod creation it stopped creating newer pods.



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