[
https://issues.apache.org/jira/browse/FLINK-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097635#comment-16097635
]
ASF GitHub Bot commented on FLINK-7241:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/4382
I would go a bit further in updating this:
- The ZooKeeper root node has a default value of `/flink` (I think). You
only need to set this when you want to organize your ZooKeeper node tree in a
specific way.
- The cluster-id docs should be changed to say that you *do not need to
set this manually* in Yarn / Mesos mode and that it generates a new subtree per
launch. You only need to set this if you want to manually recover an earlier HA
job (which is different from re-launching the job from a savepoint or
externalized checkpoint)
-
> Fix YARN high availability documentation
> ----------------------------------------
>
> Key: FLINK-7241
> URL: https://issues.apache.org/jira/browse/FLINK-7241
> Project: Flink
> Issue Type: Bug
> Components: Documentation, YARN
> Affects Versions: 1.3.0, 1.3.1
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Fix For: 1.3.2
>
>
> The documentation (jobmanager_high_availability.md) incorrectly suggests this
> configuration template when running on YARN:
> {code}
> high-availability: zookeeper
> high-availability.zookeeper.quorum: localhost:2181
> high-availability.zookeeper.storageDir: hdfs:///flink/recovery
> high-availability.zookeeper.path.root: /flink
> high-availability.zookeeper.path.namespace: /cluster_one # important:
> customize per cluster
> yarn.application-attempts: 10
> {code}
> while above it says that the namespace should not be set on YARN because it
> will be automatically generated.
> Also, the documentation still refers to {{namespace}} while this has been
> renamed to {{cluster-id}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
