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 2016/02/23 15:24:18 UTC

[jira] [Resolved] (FLINK-3410) setting setNumberOfExecutionRetries to 0 still leads to RESTARTs.

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

Till Rohrmann resolved FLINK-3410.
----------------------------------
    Resolution: Fixed

Fixed via 6323ed44d6dd051b09f9de9f8fbb95495b82cad6

> setting setNumberOfExecutionRetries to 0 still leads to RESTARTs.
> -----------------------------------------------------------------
>
>                 Key: FLINK-3410
>                 URL: https://issues.apache.org/jira/browse/FLINK-3410
>             Project: Flink
>          Issue Type: Bug
>          Components: JobManager
>    Affects Versions: 1.0.0
>            Reporter: Robert Metzger
>            Assignee: Till Rohrmann
>
> While testing the RC0 for 1.0.0 I found the following issue:
> Setting the number of retries to 0 still leads to the job being restarted:
> {code}
> final StreamExecutionEnvironment see = StreamExecutionEnvironment.getExecutionEnvironment();
> see.setNumberOfExecutionRetries(0);
> {code}
> {code}
> 21:19:50,677 INFO  org.apache.flink.runtime.jobmanager.JobManager                - Status of job 0e78d0825da485167aabee7e63c8e913 (Data Generator) changed to RESTARTING.
> 21:19:50,678 INFO  org.apache.flink.runtime.executiongraph.restart.FixedDelayRestartStrategy  - Delaying retry of job execution for 10000 ms ...
> {code}
> While looking through the code, it seems that the execution config is returning {{null}} when the number of retries is set to 0. With {{null}} the jobManager picks the default restart strategy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)