Skip to content

Commit

Permalink
[FLINK-16946] Update user documentation for job manager memory model
Browse files Browse the repository at this point in the history
This closes apache#11947.
  • Loading branch information
azagrebin authored and tillrohrmann committed May 14, 2020
1 parent ab86a3c commit d0bffc8
Show file tree
Hide file tree
Showing 19 changed files with 877 additions and 563 deletions.
21 changes: 21 additions & 0 deletions docs/fig/process_mem_model.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 3 additions & 1 deletion docs/ops/config.md
Original file line number Diff line number Diff line change
Expand Up @@ -156,7 +156,9 @@ These configuration values control the way that TaskManagers and JobManagers use
Flink tries to shield users as much as possible from the complexity of configuring the JVM for data-intensive processing.
In most cases, users should only need to set the values `taskmanager.memory.process.size` or `taskmanager.memory.flink.size` (depending on how the setup), and possibly adjusting the ratio of JVM heap and Managed Memory via `taskmanager.memory.managed.fraction`. The other options below can be used for performane tuning and fixing memory related errors.

For a detailed explanation of how these options interact, see the [documentation on TaskManager memory configuration]({{site.baseurl}}/ops/memory/mem_setup.html).
For a detailed explanation of how these options interact,
see the documentation on [TaskManager]({{site.baseurl}}/ops/memory/mem_setup_tm.html) and
[JobManager]({{site.baseurl}}/ops/memory/mem_setup_jm.html) memory configurations.

{% include generated/common_memory_section.html %}

Expand Down
4 changes: 3 additions & 1 deletion docs/ops/config.zh.md
Original file line number Diff line number Diff line change
Expand Up @@ -156,7 +156,9 @@ These configuration values control the way that TaskManagers and JobManagers use
Flink tries to shield users as much as possible from the complexity of configuring the JVM for data-intensive processing.
In most cases, users should only need to set the values `taskmanager.memory.process.size` or `taskmanager.memory.flink.size` (depending on how the setup), and possibly adjusting the ratio of JVM heap and Managed Memory via `taskmanager.memory.managed.fraction`. The other options below can be used for performane tuning and fixing memory related errors.

For a detailed explanation of how these options interact, see the [documentation on TaskManager memory configuration]({{site.baseurl}}/ops/memory/mem_setup.html).
For a detailed explanation of how these options interact,
see the documentation on [TaskManager]({{site.baseurl}}/ops/memory/mem_setup_tm.html) and
[JobManager]({{site.baseurl}}/ops/memory/mem_setup_jm.html) memory configurations.

{% include generated/common_memory_section.html %}

Expand Down
149 changes: 0 additions & 149 deletions docs/ops/memory/mem_detail.md

This file was deleted.

Loading

0 comments on commit d0bffc8

Please sign in to comment.