[
https://issues.apache.org/jira/browse/AIRFLOW-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052411#comment-17052411
]
Steven Locke commented on AIRFLOW-4515:
---------------------------------------
Yeah you could say that. We were trying to utilize the k8s executor with
our existing code base and then would have probably refactored after
getting it working. We chose to go with the standard CeleryExecutor and use
the k8s launcher instead with custom images.
That being said, I would love to move away from celery at some point.
Thanks for looking into this and sorry for the tardy reply.
Regards,
Steven Locke
--
Regards,
Steven Locke
> 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)
