[
https://issues.apache.org/jira/browse/FLINK-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015801#comment-17015801
]
Xintong Song commented on FLINK-15145:
--------------------------------------
According to the conclusion of the [ML
discussion|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Discuss-Tuning-FLIP-49-configuration-default-values-td36528.html],
we decided to make the following changes.
* Change default value of "taskmanager.memory.jvm-overhead.min" to 192MB.
* Change default value of "taskmanager.memory.jvm-metaspace.size" to 96MB.
* Change the value of "taskmanager.memory.process.size" in the default
"flink-conf.yaml" to 1568MB.
> Tune default values for FLIP-49 TM memory configurations with real production
> jobs.
> -----------------------------------------------------------------------------------
>
> Key: FLINK-15145
> URL: https://issues.apache.org/jira/browse/FLINK-15145
> Project: Flink
> Issue Type: Task
> Components: Runtime / Configuration
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In release 1.10, with FLIP-49, we introduced significant changes to the
> TaskExecutor memory model and it's related configuration options / logics.
> Since the model and configuration logics are changed, it is reasonable that
> we also change the default configuration values. Currently, the default
> values are set with the gut feelings and experiences from e2e tests. It would
> be good that we try and tune the configurations with some real production
> jobs, of various scales if possible, before exposing the configurations in
> the release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
