You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (JIRA)" <ji...@apache.org> on 2019/08/04 19:10:00 UTC
[jira] [Commented] (FLINK-13566) Support checkpoint configuration
through flink-conf.yaml
[ https://issues.apache.org/jira/browse/FLINK-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899673#comment-16899673 ]
Yun Tang commented on FLINK-13566:
----------------------------------
We could configure the checkpoint/savepoint directory but we could not configure whether to enable checkpoint, the checkpoint interval or the checkpoint mode via {{flink-conf.yaml}}. Actually, I am also been asked from our users several times why they cannot configure those but have to set programmatically. I would answer them that these parameters are used for specific jobs instead of a cluster configuration from my point of view.
Since these parameters are missing from very beginning of Flink, and thanks for [~gyfora] to bring this up. Would you or some other guys could help to answer why these parameters are missing for a long time?
> 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)