This is an automated email from the ASF dual-hosted git repository.
trohrmann pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new b23c359 [hotfix] Fix broken links in release notes for 1.11
b23c359 is described below
commit b23c3591d312dd65bacf6f0153741a17bf784a27
Author: Till Rohrmann <[email protected]>
AuthorDate: Wed Jul 1 09:34:41 2020 +0200
[hotfix] Fix broken links in release notes for 1.11
---
docs/release-notes/flink-1.11.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/release-notes/flink-1.11.md b/docs/release-notes/flink-1.11.md
index be18a0b..e32e445 100644
--- a/docs/release-notes/flink-1.11.md
+++ b/docs/release-notes/flink-1.11.md
@@ -65,7 +65,7 @@ Check the updated user documentation for [Flink Docker
integration](https://ci.a
##### Overview
With
[FLIP-116](https://cwiki.apache.org/confluence/display/FLINK/FLIP-116%3A+Unified+Memory+Configuration+for+Job+Managers),
a new memory model has been introduced for the Flink Master. New configuration
options have been introduced to control the memory consumption of the Flink
Master process. This affects all types of deployments: standalone, YARN, Mesos,
and the new active Kubernetes integration.
-Please, check the user documentation for [more
details](https://ci.apache.org/projects/flink/flink-docs-master/ops/memory/mem_setup_master.html).
+Please, check the user documentation for [more
details](https://ci.apache.org/projects/flink/flink-docs-master/ops/memory/mem_setup_jobmanager.html).
If you try to reuse your previous Flink configuration without any adjustments,
the new memory model can result in differently computed memory parameters for
the JVM and, thus, performance changes or even failures. See also [the
migration
guide](https://ci.apache.org/projects/flink/flink-docs-master/ops/memory/mem_migration.html#migrate-job-manager-memory-configuration).
@@ -75,8 +75,8 @@ The following options are deprecated:
* `jobmanager.heap.mb`
If these deprecated options are still used, they will be interpreted as one of
the following new options in order to maintain backwards compatibility:
- * [JVM
Heap](https://ci.apache.org/projects/flink/flink-docs-master/ops/memory/mem_setup_master.html#configure-jvm-heap)
([`jobmanager.memory.heap.size`](https://ci.apache.org/projects/flink/flink-docs-master/ops/config.html#jobmanager-memory-heap-size))
for standalone and Mesos deployments
- * [Total Process
Memory](https://ci.apache.org/projects/flink/flink-docs-master/ops/memory/mem_setup_master.html#configure-total-memory)
([`jobmanager.memory.process.size`](https://ci.apache.org/projects/flink/flink-docs-master/ops/config.html#jobmanager-memory-process-size))
for containerized deployments (Kubernetes and Yarn)
+ * [JVM
Heap](https://ci.apache.org/projects/flink/flink-docs-master/ops/memory/mem_setup_jobmanager.html#configure-jvm-heap)
([`jobmanager.memory.heap.size`](https://ci.apache.org/projects/flink/flink-docs-master/ops/config.html#jobmanager-memory-heap-size))
for standalone and Mesos deployments
+ * [Total Process
Memory](https://ci.apache.org/projects/flink/flink-docs-master/ops/memory/mem_setup_jobmanager.html#configure-total-memory)
([`jobmanager.memory.process.size`](https://ci.apache.org/projects/flink/flink-docs-master/ops/config.html#jobmanager-memory-process-size))
for containerized deployments (Kubernetes and Yarn)
The following options have been removed and have no effect anymore:
* `containerized.heap-cutoff-ratio`
