You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by rm...@apache.org on 2021/05/07 06:43:40 UTC
[flink] 02/02: [hotfix] Make reactive warning less strong,
clarifications
This is an automated email from the ASF dual-hosted git repository.
rmetzger pushed a commit to branch release-1.13
in repository https://gitbox.apache.org/repos/asf/flink.git
commit da9cb972bea65b47e2bfb20cebb1dd859ae338f9
Author: Robert Metzger <rm...@apache.org>
AuthorDate: Thu May 6 10:44:15 2021 +0200
[hotfix] Make reactive warning less strong, clarifications
---
docs/content.zh/docs/deployment/elastic_scaling.md | 6 +++---
docs/content/docs/deployment/elastic_scaling.md | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/content.zh/docs/deployment/elastic_scaling.md b/docs/content.zh/docs/deployment/elastic_scaling.md
index 8a06749..e4046ce 100644
--- a/docs/content.zh/docs/deployment/elastic_scaling.md
+++ b/docs/content.zh/docs/deployment/elastic_scaling.md
@@ -31,7 +31,7 @@ This page describes options where Flink automatically adjusts the parallelism in
## Reactive Mode
-{{< hint danger >}}
+{{< hint info >}}
Reactive mode is an MVP ("minimum viable product") feature. The Flink community is actively looking for feedback by users through our mailing lists. Please check the limitations listed on this page.
{{< /hint >}}
@@ -122,8 +122,8 @@ The [limitations of Adaptive Scheduler](#limitations-1) also apply to Reactive M
## Adaptive Scheduler
-{{< hint danger >}}
-Using Adaptive Scheduler directly (not through Reactive Mode) is only advised for advanced users.
+{{< hint warning >}}
+Using Adaptive Scheduler directly (not through Reactive Mode) is only advised for advanced users because slot allocation on a session cluster with multiple jobs is not defined.
{{< /hint >}}
The Adaptive Scheduler can adjust the parallelism of a job based on available slots. It will automatically reduce the parallelism if not enough slots are available to run the job with the originally configured parallelism; be it due to not enough resources being available at the time of submission, or TaskManager outages during the job execution. If new slots become available the job will be scaled up again, up to the configured parallelism.
diff --git a/docs/content/docs/deployment/elastic_scaling.md b/docs/content/docs/deployment/elastic_scaling.md
index 8a06749..e4046ce 100644
--- a/docs/content/docs/deployment/elastic_scaling.md
+++ b/docs/content/docs/deployment/elastic_scaling.md
@@ -31,7 +31,7 @@ This page describes options where Flink automatically adjusts the parallelism in
## Reactive Mode
-{{< hint danger >}}
+{{< hint info >}}
Reactive mode is an MVP ("minimum viable product") feature. The Flink community is actively looking for feedback by users through our mailing lists. Please check the limitations listed on this page.
{{< /hint >}}
@@ -122,8 +122,8 @@ The [limitations of Adaptive Scheduler](#limitations-1) also apply to Reactive M
## Adaptive Scheduler
-{{< hint danger >}}
-Using Adaptive Scheduler directly (not through Reactive Mode) is only advised for advanced users.
+{{< hint warning >}}
+Using Adaptive Scheduler directly (not through Reactive Mode) is only advised for advanced users because slot allocation on a session cluster with multiple jobs is not defined.
{{< /hint >}}
The Adaptive Scheduler can adjust the parallelism of a job based on available slots. It will automatically reduce the parallelism if not enough slots are available to run the job with the originally configured parallelism; be it due to not enough resources being available at the time of submission, or TaskManager outages during the job execution. If new slots become available the job will be scaled up again, up to the configured parallelism.