[jira] [Commented] (AIRFLOW-6535) add exception subclass to fail immediately without retrying

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124555#comment-17124555 ] 

ASF GitHub Bot commented on AIRFLOW-6535:
-----------------------------------------

marshall7m commented on pull request #7133:
URL: https://github.com/apache/airflow/pull/7133#issuecomment-637924361


   Hi there, just wondering what version of airflow the AirflowFailException is available on. Thanks!


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> add exception subclass to fail immediately without retrying
> -----------------------------------------------------------
>
>                 Key: AIRFLOW-6535
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6535
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: documentation, models
>    Affects Versions: 1.10.10
>            Reporter: Jon Stern
>            Priority: Minor
>             Fix For: 1.10.11
>
>
> I would like to be able to configure certain tasks to retry, but to also have a way to bypass retry if I can detect a condition that is unlikely to be change for the better.
> For example, imagine I have a DAG with a large number of tasks that fetch data from an API ... sometimes the API returns a 200 and everything is fine, sometimes the API returns a 500 and I know this means that API is failing under load and I want to retry later, and sometimes the API returns a 400 indicating that I've configured my requests in a way that will never succeed. If the API returns a 400 for some/all of my tasks, then I have to wait for all of them to get through all their retries before the run fails.
> My proposal is to add another subclass of AirflowException called AirflowFailException, and to update the exception handling in TaskInstance.run_raw_task such that when this exception is seen, the resulting behavior is that same as if we entered handle_failure and is_eligible_for_returned false (except with adjusted logging so it does not look like we simply hit our retry limit). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)