[
https://issues.apache.org/jira/browse/FLINK-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382528#comment-15382528
]
ASF GitHub Bot commented on FLINK-4166:
---------------------------------------
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/2249#discussion_r71178603
--- Diff: docs/setup/config.md ---
@@ -272,7 +272,9 @@ For example when running Flink on YARN on an
environment with a restrictive fire
- `recovery.zookeeper.quorum`: Defines the ZooKeeper quorum URL which is
used to connet to the ZooKeeper cluster when the 'zookeeper' recovery mode is
selected
-- `recovery.zookeeper.path.root`: (Default '/flink') Defines the root dir
under which the ZooKeeper recovery mode will create znodes.
+- `recovery.zookeeper.path.root`: (Default '/flink') Defines the root dir
under which the ZooKeeper recovery mode will create namespace directories.
+
+- `recovery.zookeeper.path.namespace`: (Default '/default_ns' in
standalone mode, or the <yarn-application-id> under Yarn) Defines the
subdirectory under the root dir where the ZooKeeper recovery mode will create
znodes. This allows to isolate multiple applications on the same ZooKeeper.
--- End diff --
It would be nice to have a default namespace for the standalone mode as
well. How about generating a namespace from the `masters` files. Would hashing
the contents of the file be a good fit? That should be consistent across all
master nodes.
> Generate automatic different namespaces in Zookeeper for Flink applications
> ---------------------------------------------------------------------------
>
> Key: FLINK-4166
> URL: https://issues.apache.org/jira/browse/FLINK-4166
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.0.3
> Reporter: Stefan Richter
>
> We should automatically generate different namespaces per Flink application
> in Zookeeper to avoid interference between different applications that refer
> to the same Zookeeper entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
