You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/12/30 02:29:00 UTC
[jira] [Updated] (FLINK-15367) Handle backwards compatibility of
"taskmanager.heap.size" differently for standalone / active setups
[ https://issues.apache.org/jira/browse/FLINK-15367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-15367:
-----------------------------------
Labels: pull-request-available (was: )
> Handle backwards compatibility of "taskmanager.heap.size" differently for standalone / active setups
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-15367
> URL: https://issues.apache.org/jira/browse/FLINK-15367
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
>
> Previously, "taskmanager.heap.size" were used differently for calculating TM memory sizes on standalone / active setups. To fully align with the previous behaviors, we need to map this deprecated key to "taskmanager.memory.flink.size" for standalone setups and "taskmanager.memory.process.size" for active setups.
> Detailed discussion can be found in this [ML thread|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Some-feedback-after-trying-out-the-new-FLIP-49-memory-configurations-td36129.html].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)