You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by al...@apache.org on 2017/07/24 16:37:37 UTC

[2/3] flink git commit: [FLINK-7241] Remove cluster-id from YARN HA setup template in doc

[FLINK-7241] Remove cluster-id from YARN HA setup template in doc

When running a YARN cluster the cluster-id is automatically derived.
Acutally setting a cluster-id can lead to problems if you start multiple
per-job YARN sessions with the same cluster-id by accident.


Project: http://git-wip-us.apache.org/repos/asf/flink/repo
Commit: http://git-wip-us.apache.org/repos/asf/flink/commit/d628e7a7
Tree: http://git-wip-us.apache.org/repos/asf/flink/tree/d628e7a7
Diff: http://git-wip-us.apache.org/repos/asf/flink/diff/d628e7a7

Branch: refs/heads/master
Commit: d628e7a7b45aa3d82a9195dc227c1067151d9c99
Parents: a671035
Author: Aljoscha Krettek <al...@gmail.com>
Authored: Fri Jul 21 17:46:25 2017 +0200
Committer: Aljoscha Krettek <al...@gmail.com>
Committed: Mon Jul 24 18:36:48 2017 +0200

----------------------------------------------------------------------
 docs/setup/jobmanager_high_availability.md | 1 -
 1 file changed, 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/flink/blob/d628e7a7/docs/setup/jobmanager_high_availability.md
----------------------------------------------------------------------
diff --git a/docs/setup/jobmanager_high_availability.md b/docs/setup/jobmanager_high_availability.md
index e770fa8..8754537 100644
--- a/docs/setup/jobmanager_high_availability.md
+++ b/docs/setup/jobmanager_high_availability.md
@@ -187,7 +187,6 @@ 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.cluster-id: /cluster_one # important: customize per cluster
 yarn.application-attempts: 10</pre>
 
 3. **Configure ZooKeeper server** in `conf/zoo.cfg` (currently it's only possible to run a single ZooKeeper server per machine):