[
https://issues.apache.org/jira/browse/FLINK-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984741#comment-14984741
]
Stephan Ewen commented on FLINK-2929:
-------------------------------------
I think not purging on start is a good idea for exactly the reasons you
mentioned (upgrades, etc) and since you can always cancel/stop the job
explicitly, you can work around that.
> Recovery of jobs on cluster restarts
> ------------------------------------
>
> Key: FLINK-2929
> URL: https://issues.apache.org/jira/browse/FLINK-2929
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 0.10
> Reporter: Ufuk Celebi
>
> Recovery information is stored in ZooKeeper under a static root like
> {{/flink}}. In case of a cluster restart without canceling running jobs old
> jobs will be recovered from ZooKeeper.
> This can be confusing or helpful depending on the use case.
> I suspect that the confusing case will be more common.
> We can change the default cluster start up (e.g. new YARN session or new
> ./start-cluster call) to purge all existing data in ZooKeeper and add a flag
> to not do this if needed.
> [~trohrm...@apache.org], [~aljoscha], [~StephanEwen] what's your opinion?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
