Hi Vera,
Apparently, if there no job-specific restart strategy, an infinite
FixedDelayRestartStrategy is always used for the job submission:
https://github.com/apache/flink/blob/master/flink-streaming-java/src/main/java/org/apache/flink/streaming/api/graph/StreamingJobGraphGenerator.java#L571-L576
IMO, this seems to be a bug, as the global restart strategy config should be
respected. I’ll get back to this once I confirm this.
Regards,
Gordon
On 28 June 2017 at 10:22:37 PM, Vera Coberley (veracober...@gmail.com) wrote:
Hi all,
We are running Flink 1.2.0. Our flink-conf.yaml is configured to use a default
restart-strategy of fixed-delay, with 3 attempts:
restart-strategy: fixed-delay
restart-strategy.fixed-delay.attempts: 3
These settings are echoed by the GlobalConfiguration (see first set of log
statements). However, the job is submitted with a maxNumberRestartAttempts of
Max INT instead of 3 (see second set of log statements)
The job is enabled for checkpointing, and it does not have any job-specific
restart strategy defined:
StreamExecutionEnvironment env =
StreamExecutionEnvironment.getExecutionEnvironment();
env.enableCheckpointing(params.getLong("checkpoint.interval", 3000L));
I assumed the default restart configuration would carry over to the job. Am I
mistaken in my assumption, do I have a configuration error, or is this a bug?
-- Vera
2017-06-27 19:52:11.288 [main] INFO
org.apache.flink.configuration.GlobalConfiguration - Loading configuration
property: restart-strategy, fixed-delay
2017-06-27 19:52:11.288 [main] INFO
org.apache.flink.configuration.GlobalConfiguration - Loading configuration
property: restart-strategy.fixed-delay.attempts, 3
2017-06-27 19:52:17.642 [flink-akka.actor.default-dispatcher-16] INFO
org.apache.flink.yarn.YarnJobManager - Submitting job XYZ
2017-06-27 19:52:17.652 [flink-akka.actor.default-dispatcher-16] INFO
org.apache.flink.yarn.YarnJobManager - Using restart strategy
FixedDelayRestartStrategy(maxNumberRestartAttempts=2147483647,
delayBetweenRestartAttempts=10000) for XYZ
