[
https://issues.apache.org/jira/browse/AIRFLOW-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894822#comment-16894822
]
Steven Locke commented on AIRFLOW-4515:
---------------------------------------
[~davlum] I definitely believe you, however, I am confused as to how I should
be calling the SubdagOperator then. I followed the example in the source code
[https://github.com/apache/airflow/blob/1.10.3/airflow/operators/subdag_operator.py#L49]
which passes an instance of an executor in. And the executor init doesn't take
any arguments
[https://github.com/apache/airflow/blob/1.10.3/airflow/contrib/executors/kubernetes_executor.py#L596]
.
Is there any additional documentation you can link?
> KubernetesExecutor hangs in the subdag context
> ----------------------------------------------
>
> Key: AIRFLOW-4515
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4515
> Project: Apache Airflow
> Issue Type: Bug
> Components: executors
> Affects Versions: 1.10.3
> Reporter: Steven Locke
> Assignee: Daniel Imberman
> Priority: Major
> Labels: kubernetes
>
> The bug is that when using the kubernetes executor in a k8s cluster and
> running a subdag with `executor=KubernetesExecutor()` the subdag never
> returns. Just runs infinitely. Here is an example repo
> https://github.com/slocke716/test_subdags
> This is occurring on 1.10.3 1.10.3post1 and 1.10.3b2 at least
> Not passing `executor=KubernetesExecutor()` into the subdag operator is not
> an option since it defaults to the SequentialExecutor and changing to the
> LocalExecutor causes thread errors because we require quite a bit of
> concurrency
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
