[
https://issues.apache.org/jira/browse/AIRFLOW-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000228#comment-17000228
]
David Lum commented on AIRFLOW-4515:
------------------------------------
Sorry I mistook the argument you're passing. I thought you were talking about
the `executor_config` argument. Yeah this looks like a bug. I also find the
SubDag operator to be quite buggy with the KubernetesExecutor, even when
running the SequentialExecutor. It has a possibility of queuing tasks but never
running them it seems.
Not really adressing the bug, but if your premise is to run the Subdag with the
KubernetesExecutor, Isn't this functionally the same as not using the Subdag?
> 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
(v8.3.4#803005)
