[
https://issues.apache.org/jira/browse/FLINK-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973870#comment-16973870
]
Xintong Song commented on FLINK-13982:
--------------------------------------
Hi [~dwysakowicz],
Sorry for causing the confusion. True, I should add a link to the new
alternative. In the PR of this issue, the new alternative is
{{TaskManagerOptions#TOTAL_FLINK_MEMORY}}. The reason you find that the
description of the old key is updated, is because it is added as a deprecated
key for the new option.
Above are the status by the time this issue is closed. According to our latest
findings in backwards capability and e2e tests, we decided to bind
{{TaskManagerOptions#TASK_MANAGER_HEAP_MEMORY}} to
{{TaskManagerOptions#TOTAL_PROCESS_MEMORY}} rather than
{{TaskManagerOptions#TOTAL_FLINK_MEMORY}} (PR is under review). In addition,
the deprecated config options (whose keys are already added as deprecated keys
of new options) will be removed in our follow-up PR for cleaning up legacy
codes.
> Implement memory calculation logics
> -----------------------------------
>
> Key: FLINK-13982
> URL: https://issues.apache.org/jira/browse/FLINK-13982
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> * Introduce new configuration options
> * Introduce data structures and utilities.
> ** Data structure to store memory / pool sizes of task executor
> ** Utility for calculating memory / pool sizes from configuration
> ** Utility for generating dynamic configurations
> ** Utility for generating JVM parameters
> This step should not introduce any behavior changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
