flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-17714) Support custom RestartBackoffTimeStrategy
Date Tue, 25 May 2021 22:57:00 GMT

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

Flink Jira Bot updated FLINK-17714:
-----------------------------------
    Labels: stale-major  (was: )

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community
manage its development. I see this issues has been marked as Major but is unassigned and neither
itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major"
to the issue". If this ticket is a Major, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Support custom RestartBackoffTimeStrategy
> -----------------------------------------
>
>                 Key: FLINK-17714
>                 URL: https://issues.apache.org/jira/browse/FLINK-17714
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Zhu Zhu
>            Priority: Major
>              Labels: stale-major
>
> There are cases that users need to customize RestartBackoffTimeStrategy to better control
job recovery. 
> One example is that users want a job to restart only on certain errors and fail on others.
See this ML [disscusion|https://lists.apache.org/thread.html/rde685552a83d0d146cf83560df1bc6f33d3dd569f69ae7bbcc4ae508%40%3Cuser.flink.apache.org%3E].



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

Mime
View raw message