[
https://issues.apache.org/jira/browse/FLINK-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900096#comment-16900096
]
Ufuk Celebi commented on FLINK-13566:
-------------------------------------
I see that having a good default checkpointing interval for session clusters
with many different kind of jobs can be challenging, but overall the analogy to
default state backend configuration makes sense to me. In application cluster
environments which are becoming more commonly used the argument about job vs.
cluster-level configuration actually doesn't even apply.
I think this ticket warrants a small summary document with how this behaves
with interesting configuration combinations. For instance, if we can enable
checkpointing by default, do we need to allow users to specifically disable
checkpointing via their env? Can there be problems activating checkpointing by
default?
[~gyfora] Are you planning to work on this?
[~aljoscha] What do you think about this?
> Support checkpoint configuration through flink-conf.yaml
> --------------------------------------------------------
>
> Key: FLINK-13566
> URL: https://issues.apache.org/jira/browse/FLINK-13566
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Checkpointing, Runtime / Configuration
> Reporter: Gyula Fora
> Priority: Major
>
> Currently basic checkpointing configuration happens through the
> StreamExecutionEnvironment and the CheckpointConfig class.
> There is no way to configure checkpointing behaviour purely from the
> flink-conf.yaml file (or provide a default checkpointing behaviour) as it
> always needs to happen programmatically through the environment.
> The checkpoint config settings are then translated down to the
> CheckpointCoordinatorConfiguration which will control the runtime behaviour.
> As checkpointing related settings are operational features that should not
> affect the application logic I think we need to support configuring these
> params through the flink-conf yaml.
> In order to do this we probably need to rework the CheckpointConfig class so
> that it distinguishes parameters that the user actually set from the defaults
> (to support overriding what was set in the conf).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
