Skip to content

[FLINK-14123]Update help docs for OutOfMemoryError #278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: asf-site
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions gettinghelp.md
Original file line number Diff line number Diff line change
Expand Up @@ -131,3 +131,12 @@ Hadoop version of the cluster you want to connect to (HDFS / YARN).

The easiest way to fix that is to pick a Hadoop-free Flink version and simply export the Hadoop path and
classpath from the cluster.

### I have an OutOfMemoryError

In Fink 1.9.0 and prior version, the managed memory fraction of taskmanager is controlled by `taskmanager.memory.fraction`,
and with 0.7 as the default value. This sometimes will cause OOMs due to the fact that the default value of
JVM parameter `NewRatio` is 2, which means the old generation occupied only 2/3 (0.66) of the heap memory.
Comment on lines +137 to +139
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In Fink 1.9.0 and prior version, the managed memory fraction of taskmanager is controlled by `taskmanager.memory.fraction`,
and with 0.7 as the default value. This sometimes will cause OOMs due to the fact that the default value of
JVM parameter `NewRatio` is 2, which means the old generation occupied only 2/3 (0.66) of the heap memory.
In Flink 1.9.0 and prior versions, the managed memory fraction of the taskmanager is controlled by `taskmanager.memory.fraction`,
with 0.7 as the default value. This will sometimes cause OOMs because the default value of the
JVM parameter `NewRatio` is 2, which means that the old generation occupied only 2/3 (0.66) of the heap memory.


If you run into this case, please try to manually change this value to a lower value.