We have the exact same problem. In our case, it's a bash operator starting
a docker container. The container and process it ran exit, but the 'docker
run' command is still showing up in the process table, waiting for an event.
I'm trying to switch to LocalExecutor to see if that will help.
_jonas
On Thu, Jul 27, 2017 at 4:28 PM Marc Weil <mw...@newrelic.com> wrote:
> Hello,
>
> Has anyone seen the behavior when using CeleryExecutor where workers will
> finish their tasks ("INFO - Task exited with return code 0" shows in the
> logs) but are never marked as complete in the airflow DB or UI? Effectively
> this causes tasks to hang even though they are complete, and the DAG will
> not continue.
>
> This is happening on 1.8.0. Anyone else seen this or perhaps have a
> workaround?
>
> Thanks!
>
> --
> Marc Weil | Lead Engineer | Growth Automation, Marketing, and Engagement |
> New Relic
> ᐧ
>
