zachliu opened a new pull request #22002:
URL: https://github.com/apache/airflow/pull/22002


   In an old PR https://github.com/apache/airflow/pull/14263 we tried to add a 
"retry" mechanism for triggering new ECS task but it didn't work as expected 
according to my explanation in https://github.com/apache/airflow/pull/16150. 
   
   The TL;DR version is: 
   
   * The immediate API response after sending out the `run_task` request to aws 
is not reliable. To make sure our task is really running in good health, we 
have to wait and send out another `describe_tasks` request.
   
   
   This explanation still holds today. Since people start using Fargate 
nowadays, this issue becomes more and more acute. On a good day, 0.15% Fargate 
tasks could fail to start due to ENI (AWS Elastic Network Interface) provision 
failures. However on a bad day, it could rise to 1~2%.
   
   Per recommendations from the AWS support team, we should consider the 
"triggering an ECS task, waiting for it to be provisioned, checking for its 
status" steps a single routine that can be retried as a whole.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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]


Reply via email to