From a730f5d2c1b6673de55b0272f5a037245db89303 Mon Sep 17 00:00:00 2001 From: yanghua Date: Wed, 9 May 2018 20:13:18 +0800 Subject: [PATCH 1/3] [FLINK-9309] Recommend HA setup on Production Readiness Checklist --- docs/ops/production_ready.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/ops/production_ready.md b/docs/ops/production_ready.md index 0d11b8a1866b1..4ff0f967231d6 100644 --- a/docs/ops/production_ready.md +++ b/docs/ops/production_ready.md @@ -87,4 +87,15 @@ you are sure that your state will never exceed main memory and blocking the stre you **could consider** to not use the RocksDB backends. However, at this point, we **strongly recommend** using RocksDB for production. +### Config JobManager High Availability(HA) + +The JobManager coordinates every Flink deployment. It is responsible for both *scheduling* and *resource management*. + +By default, there is a single JobManager instance per Flink cluster. This creates a *single point of failure* (SPOF): +if the JobManager crashes, no new programs can be submitted and running programs fail. + +With JobManager High Availability, you can recover from JobManager failures and thereby eliminate the *SPOF*. +You can configure high availability for both [**standalone**]({{ site.baseurl }}/ops/jobmanager_high_availability.html#standalone-cluster-high-availability) +and [**YARN clusters**]({{ site.baseurl }}/ops/jobmanager_high_availability.html#yarn-cluster-high-availability). + {% top %} From 7e95e1c60ab621d6ad74d3c29bf7240f3b8e8792 Mon Sep 17 00:00:00 2001 From: yanghua Date: Thu, 10 May 2018 10:45:01 +0800 Subject: [PATCH 2/3] refactor the description and removed the link to specific deploy mode --- docs/ops/production_ready.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/ops/production_ready.md b/docs/ops/production_ready.md index 4ff0f967231d6..0eb6a8ed0b394 100644 --- a/docs/ops/production_ready.md +++ b/docs/ops/production_ready.md @@ -95,7 +95,6 @@ By default, there is a single JobManager instance per Flink cluster. This create if the JobManager crashes, no new programs can be submitted and running programs fail. With JobManager High Availability, you can recover from JobManager failures and thereby eliminate the *SPOF*. -You can configure high availability for both [**standalone**]({{ site.baseurl }}/ops/jobmanager_high_availability.html#standalone-cluster-high-availability) -and [**YARN clusters**]({{ site.baseurl }}/ops/jobmanager_high_availability.html#yarn-cluster-high-availability). +We **strongly recommend** you configure []high availability]({{ site.baseurl }}/ops/jobmanager_high_availability.html) for production. {% top %} From e8093ade99c6d10d119761d710f97841376a1d6a Mon Sep 17 00:00:00 2001 From: yanghua Date: Thu, 10 May 2018 10:46:55 +0800 Subject: [PATCH 3/3] fixed a hyperlink problem --- docs/ops/production_ready.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ops/production_ready.md b/docs/ops/production_ready.md index 0eb6a8ed0b394..08fef2bb10d66 100644 --- a/docs/ops/production_ready.md +++ b/docs/ops/production_ready.md @@ -95,6 +95,6 @@ By default, there is a single JobManager instance per Flink cluster. This create if the JobManager crashes, no new programs can be submitted and running programs fail. With JobManager High Availability, you can recover from JobManager failures and thereby eliminate the *SPOF*. -We **strongly recommend** you configure []high availability]({{ site.baseurl }}/ops/jobmanager_high_availability.html) for production. +We **strongly recommend** you configure [high availability]({{ site.baseurl }}/ops/jobmanager_high_availability.html) for production. {% top %}