[GitHub] [airflow] zachliu commented on issue #15000: When an ECS Task fails to start, ECS Operator raises a CloudWatch exception

2021-09-28 Thread GitBox
zachliu commented on issue #15000: URL: https://github.com/apache/airflow/issues/15000#issuecomment-928219338 > @zachliu @kanga333 did remove retry for now #16150 solved the problem? @eladkal unfortunately no, #16150 was for another issue that's only somewhat related to this one

[GitHub] [airflow] zachliu commented on issue #15000: When an ECS Task fails to start, ECS Operator raises a CloudWatch exception

2021-09-27 Thread GitBox
zachliu commented on issue #15000: URL: https://github.com/apache/airflow/issues/15000#issuecomment-928219338 > @zachliu @kanga333 did remove retry for now #16150 solved the problem? @eladkal unfortunately no, #16150 was for another issue that's only somewhat related to this one

[GitHub] [airflow] zachliu commented on issue #15000: When an ECS Task fails to start, ECS Operator raises a CloudWatch exception

2021-04-21 Thread GitBox
zachliu commented on issue #15000: URL: https://github.com/apache/airflow/issues/15000#issuecomment-824404502 Yes. And Fargate tasks are more likely to experience this `failed-to-start` issue than the conventional EC2 tasks. I've been back and forth with AWS support on this one for a long