[
https://issues.apache.org/jira/browse/FLINK-32895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763530#comment-17763530
]
Zhu Zhu commented on FLINK-32895:
---------------------------------
Either option sounds good to me. Feel free to start the discussion earlier if
you feel there are much uncertainty which needs to be addressed earlier.
> user may want to restart this job multiple times using max-backoff before
> failing it.
Yes you are right. Yet maybe we can give it a more user friendly name. e.g.
`max-attempts-before-reset-backoff` looks better to me.
> Introduce the max attempts for Exponential Delay Restart Strategy
> -----------------------------------------------------------------
>
> Key: FLINK-32895
> URL: https://issues.apache.org/jira/browse/FLINK-32895
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
>
> Currently, Flink has 3 restart strategies, they are: fixed-delay,
> failure-rate and exponential-delay.
> The exponential-delay is suitable if a job continues to fail for a period of
> time. The fixed-delay and failure-rate has the max attempts mechanism, that
> means, the job won't restart and go to fail after the attempt exceeds the
> threshold of max attempts.
> The max attempts mechanism is reasonable, flink should not or need to
> infinitely restart the job if the job keeps failing. However, the
> exponential-delay doesn't have the max attempts mechanism.
> I propose introducing the
> `restart-strategy.exponential-delay.max-attempts-before-reset` to support the
> max attempts mechanism for exponential-delay. It means flink won't restart
> job if the number of job failures before reset exceeds
> max-attempts-before-reset when is exponential-delay is enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
