o-nikolas commented on issue #32943: URL: https://github.com/apache/airflow/issues/32943#issuecomment-1670013855
> EcsExecutor will act like a KubernetesExecturor ( one new ephemeral airflow worker container for every task ) or CeleryExecutor ( shared running container for N airflow task ) , or a mix of both ( like the CeleryKubernetesExecutor ) ? It will work much like the K8s executor, with each Airflow Task launched into it's own ECS Task (the overloading of the word Task is very unfortunate in this space :laughing: ) > will the EcsExecutor support/manage the triggerer(s) for the deferable tasks ? It is not really up to the executor to manager deferred tasks. That is the responsibility of the Triggerer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
