Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1470#issuecomment-183268932
Alright, I've reintroduced the old execution attempts and delay
configuration values and the API calls at the `ExecutionEnvironment`.
The behaviour is now the following:
1. If an explicit `RestartStrategy` is set for a job, it is taken.
2. Otherwise it is checked whether the number of retries and retry delay
has been set at the `ExecutionEnvironment`/`ExecutionConfig`. If this is the
case, then a `FixedDelayRestartStrategy` is instantiated with these values.
3. If no explicit `RestartStrategy` has been defined for the job, then the
default restart strategy of the `JobManager` is used. The default restart
strategy is defined the following way:
3.1. If the configuration contains a configuration value
`restart-strategy`, then this defines the used `RestartStrategy`.
3.2. If `restart-strategy` is not set, then the old
`execution-retries.default` and `execution-retries.delay` configuration values
are checked. If they are set with `execution-retries.default > 0` and
`execution-retries.delay >= 0`, then a `FixedDelayRestartStrategy` is
instantiated with the respective values. This is then used as the default
restart strategy. If these values are not defined, then a `NoRestartStrategy`
is instantiated.
This should be not API breaking unless people used the
`setExecutionRetries` at the `JobGraph` or the `Plan`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
