Kubernetes Executor wastefully creates pods for DummyOperator tasks

[jpuffer]

Description

Kubernetes Executor currently spins up a whole worker pod to execute a dummy task. We know Airflow's DummyOperator doesn't actually do work - it's there to help to organize /group tasks and very useful for that purpose.

Use case / motivation

For complex DAGs, skipping the worker creation process for dummy tasks could significantly improve execution time and resource use in the cluster. Could the executor work more like the local executor when dealing with the dummy tasks? (that way, they could be essentially instant and not interfere with the actual worker pool)

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[mik-laj]

Interesting idea. I think you can just mark these tasks automatically in a success state. This made this change work for all executors.

[mik-laj]

Done :-D

[jpuffer]

🌟⚡️🎉

…

On Thu, Mar 26, 2020 at 1:49 PM Kamil Breguła ***@***.***> wrote: Done :-D — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7871 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAS273TBIKZJG5FY76UFIYTRJOIRTANCNFSM4LTSIZKA> .