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:38 UTC
[flink] branch release-1.13 updated (c8b3160 -> da9cb97)
This is an automated email from the ASF dual-hosted git repository.
rmetzger pushed a change to branch release-1.13
in repository https://gitbox.apache.org/repos/asf/flink.git.
from c8b3160 [hotfix][docs][python] Add an overview page for Python UDFs
new 8094c0f [hotfix][docs] Re-introduce note about FLINK_CONF_DIR
new da9cb97 [hotfix] Make reactive warning less strong, clarifications
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/content.zh/docs/deployment/config.md | 4 ++++
docs/content.zh/docs/deployment/elastic_scaling.md | 6 +++---
docs/content/docs/deployment/config.md | 4 ++++
docs/content/docs/deployment/elastic_scaling.md | 6 +++---
4 files changed, 14 insertions(+), 6 deletions(-)
[flink] 01/02: [hotfix][docs] Re-introduce note about FLINK_CONF_DIR
Posted by rm...@apache.org.
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 8094c0f85bd3e3382bcc19d5097ef51c93ad3f82
Author: Robert Metzger <rm...@apache.org>
AuthorDate: Thu May 6 10:51:21 2021 +0200
[hotfix][docs] Re-introduce note about FLINK_CONF_DIR
This closes #15845
---
docs/content.zh/docs/deployment/config.md | 4 ++++
docs/content/docs/deployment/config.md | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/docs/content.zh/docs/deployment/config.md b/docs/content.zh/docs/deployment/config.md
index 92b5903..14806f9 100644
--- a/docs/content.zh/docs/deployment/config.md
+++ b/docs/content.zh/docs/deployment/config.md
@@ -34,6 +34,10 @@ The configuration is parsed and evaluated when the Flink processes are started.
The out of the box configuration will use your default Java installation. You can manually set the environment variable `JAVA_HOME` or the configuration key `env.java.home` in `conf/flink-conf.yaml` if you want to manually override the Java runtime to use.
+You can specify a different configuration directory location by defining the `FLINK_CONF_DIR` environment variable. For resource providers which provide non-session deployments, you can specify per-job configurations this way. Make a copy of the `conf` directory from the Flink distribution and modify the settings on a per-job basis. Note that this is not supported in Docker or standalone Kubernetes deployments. On Docker-based deployments, you can use the `FLINK_PROPERTIES` environment v [...]
+
+On session clusters, the provided configuration will only be used for configuring [execution](#execution) parameters, e.g. configuration parameters affecting the job, not the underlying cluster.
+
# Basic Setup
The default configuration supports starting a single-node Flink session cluster without any changes.
diff --git a/docs/content/docs/deployment/config.md b/docs/content/docs/deployment/config.md
index 3310a15..935e791 100644
--- a/docs/content/docs/deployment/config.md
+++ b/docs/content/docs/deployment/config.md
@@ -34,6 +34,10 @@ The configuration is parsed and evaluated when the Flink processes are started.
The out of the box configuration will use your default Java installation. You can manually set the environment variable `JAVA_HOME` or the configuration key `env.java.home` in `conf/flink-conf.yaml` if you want to manually override the Java runtime to use.
+You can specify a different configuration directory location by defining the `FLINK_CONF_DIR` environment variable. For resource providers which provide non-session deployments, you can specify per-job configurations this way. Make a copy of the `conf` directory from the Flink distribution and modify the settings on a per-job basis. Note that this is not supported in Docker or standalone Kubernetes deployments. On Docker-based deployments, you can use the `FLINK_PROPERTIES` environment v [...]
+
+On session clusters, the provided configuration will only be used for configuring [execution](#execution) parameters, e.g. configuration parameters affecting the job, not the underlying cluster.
+
# Basic Setup
The default configuration supports starting a single-node Flink session cluster without any changes.
[flink] 02/02: [hotfix] Make reactive warning less strong,
clarifications
Posted by rm...@apache.org.
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.