You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/10/09 12:42:00 UTC

[jira] [Closed] (FLINK-10298) Batch Job Failover Strategy

     [ https://issues.apache.org/jira/browse/FLINK-10298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-10298.
---------------------------------
    Resolution: Abandoned

Closing for inactivity.

> Batch Job Failover Strategy
> ---------------------------
>
>                 Key: FLINK-10298
>                 URL: https://issues.apache.org/jira/browse/FLINK-10298
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: JIN SUN
>            Assignee: ryantaocer
>            Priority: Major
>              Labels: pull-request-available
>
> The new failover strategy needs to consider handling failures according to different failure types. It orchestrates all the logics we mentioned in this [document|https://docs.google.com/document/d/1FdZdcA63tPUEewcCimTFy9Iz2jlVlMRANZkO4RngIuk/edit], we can put the logic in onTaskFailure method of the FailoverStrategy interface, with the logic inline:
> {code:java}
> public void onTaskFailure(Execution taskExecution, Throwable cause) {  
>         //1. Get the throwable type
>         //2. If the type is NonrecoverableType fail the job
>         //3. If the type is PatritionDataMissingError, do revocation
>         //4. If the type is EnvironmentError, do check blacklist
>         //5. Other failure types are recoverable, but we need to remember the count of the failure,
>         //6. if it exceeds the threshold, fail the job
> }{code}



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