Github user zentol commented on a diff in the pull request:
https://github.com/apache/flink/pull/2249#discussion_r70883081
--- Diff: docs/setup/jobmanager_high_availability.md ---
@@ -74,11 +74,15 @@ In order to start an HA-cluster add the following
configuration keys to `conf/fl
Each *addressX:port* refers to a ZooKeeper server, which is reachable by
Flink at the given address and port.
-- **ZooKeeper root** (recommended): The *root ZooKeeper node*, under which
all required coordination data is placed.
+- **ZooKeeper root** (recommended): The *root ZooKeeper node*, under which
all cluster namespace nodes are placed.
- <pre>recovery.zookeeper.path.root: /flink # important: customize per
cluster</pre>
+ <pre>recovery.zookeeper.path.root: /flink
- **Important**: if you are running multiple Flink HA clusters, you have
to manually configure separate root nodes for each cluster.
+- **ZooKeeper namespace** (recommended): The *namespace ZooKeeper node*,
under which all required coordination data for a cluster is placed.
+
+ <pre>recovery.zookeeper.path.namespace: /default_ns # important:
customize per cluster</pre>
+
+ **Important**: if you are running multiple Flink HA clusters, you have
to manually configure separate namespaces for each cluster. By default, Yarn
cluster and Yarn session automatically generate namespaces based on Yarn
application id. A manual configuration overrides this behaviour in Yarn.
Specifying a namespace with the -z CLI option, in turn, overrides manual
configuration.
--- End diff --
i believe you are missing a "the" before "Yarn cluster" and "Yarn
application id"
---
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.
---
