flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3187) Decouple restart strategy from ExecutionGraph
Date Fri, 12 Feb 2016 10:52:18 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144405#comment-15144405

ASF GitHub Bot commented on FLINK-3187:

Github user uce commented on the pull request:

    Thank you very much! Behaviour is as I would expect it.
    Last minor comment: can you add a comment in the deprecated methods (both Java and Scala)
with a reference to the restart strategy while merging? I think this will make the transition
easier for users.
    +1 to merge.

> Decouple restart strategy from ExecutionGraph
> ---------------------------------------------
>                 Key: FLINK-3187
>                 URL: https://issues.apache.org/jira/browse/FLINK-3187
>             Project: Flink
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
> Currently, the {{ExecutionGraph}} supports the following restart logic: Whenever a failure
occurs and the number of restart attempts aren't depleted, wait for a fixed amount of time
and then try to restart. This behaviour can be controlled by the configuration parameters
{{execution-retries.default}} and {{execution-retries.delay}}.
> I propose to decouple the restart logic from the {{ExecutionGraph}} a bit by introducing
a strategy pattern. That way it would not only allow us to define a job specific restart behaviour
but also to implement different restart strategies. Conceivable strategies could be: Fixed
timeout restart, exponential backoff restart, partial topology restarts, etc.
> This change is a preliminary step towards having a restart strategy which will scale
the parallelism of a job down in case that not enough slots are available.

This message was sent by Atlassian JIRA

View raw message