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-2930) ExecutionConfig execution retry delay not respected
Date Tue, 27 Oct 2015 17:18:27 GMT

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

ASF GitHub Bot commented on FLINK-2930:

GitHub user uce opened a pull request:


    [FLINK-2930] Respect ExecutionConfig execution retry delay

    This only affects job recovery on non-master failures.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/uce/flink delay

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1304
commit 7c62b7ef2b30d9a95eb661c34032d705e9e23cf4
Author: Ufuk Celebi <uce@apache.org>
Date:   2015-10-27T17:15:15Z

    [FLINK-2930] Respect ExecutionConfig execution retry delay


> ExecutionConfig execution retry delay not respected
> ---------------------------------------------------
>                 Key: FLINK-2930
>                 URL: https://issues.apache.org/jira/browse/FLINK-2930
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Runtime
>    Affects Versions: 0.10
>            Reporter: Ufuk Celebi
> Setting the execution retry delay via the ExecutionConfig is not respected by the ExecutionGraph
on restarts (this is only relevant for non-master failures).

This message was sent by Atlassian JIRA

View raw message