[
https://issues.apache.org/jira/browse/FLINK-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974009#comment-16974009
]
Dawid Wysakowicz commented on FLINK-13982:
------------------------------------------
Thanks for the explanation.
No worries. I was going through different options and their usage and was
surprised when I saw a method: {{ConfigurationUtils#getTaskManagerHeapMemory}}
that fallbacks between only deprecated options and was looking for the new
alternative. I think we should try to have it cleanly explained as it might
confuse our users as well in the end.
> 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)
