You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched in the issues and found no similar issues.
What would you like to be improved?
The current Flink optimizer mainly utilizes the heap memory of Task Manager, but Flink allocates around 50% of memory to managed memory by default, resulting in less heap memory available and increasing the risk of OOM issues for the Task Manager.
How should we improve?
To reduce the risk of OOM of Task Manager caused by unreasonable managed memory configuration, the configuration taskmanager.memory.managed.size should be explicitly specified in the doc and script of starting Flink optimizer.
And taskmanager.memory.managed.size=32mb may be a reasonable value.
The doc is here: https://github.com/NetEase/amoro/blob/master/docs/admin-guides/managing-optimizers.md#deploy-external-optimizer.
The startup script is here: com.netease.arctic.optimizer.FlinkOptimizerContainer#buildOptimizerStartupArgsString
Search before asking
What would you like to be improved?
The current Flink optimizer mainly utilizes the heap memory of Task Manager, but Flink allocates around 50% of memory to managed memory by default, resulting in less heap memory available and increasing the risk of OOM issues for the Task Manager.
How should we improve?
To reduce the risk of OOM of Task Manager caused by unreasonable managed memory configuration, the configuration
taskmanager.memory.managed.size
should be explicitly specified in the doc and script of starting Flink optimizer.And
taskmanager.memory.managed.size=32mb
may be a reasonable value.The doc is here:
https://github.com/NetEase/amoro/blob/master/docs/admin-guides/managing-optimizers.md#deploy-external-optimizer
.The startup script is here:
com.netease.arctic.optimizer.FlinkOptimizerContainer#buildOptimizerStartupArgsString
Are you willing to submit PR?
Subtasks
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: