[
https://issues.apache.org/jira/browse/FLINK-16734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321394#comment-17321394
]
Flink Jira Bot commented on FLINK-16734:
----------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> Remove ClusterSpecification
> ---------------------------
>
> Key: FLINK-16734
> URL: https://issues.apache.org/jira/browse/FLINK-16734
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client
> Reporter: Xintong Song
> Priority: Minor
> Labels: stale-minor
>
> Currently, {{ClusterSpecification}} has the following three fields.
> * masterMemoryMB
> * taskManagerMemoryMB
> * slotsPerTaskManager
> Among the three fields, {{taskManagerMemoryMB}} is only used in
> {{YarnClusterDescriptor#validateClusterResources}}. It can be replaced by
> "taskmanager.memory.process.size" in the configuration. Moreover, there are
> consistency risks for keeping the process memory in two places with different
> precision (MB vs. MemorySize).
> {{masterMemoryMB}} should be the same as {{taskManagerMemoryMB}} after
> finishing [FLIP-116 Unified Memory Configuration for Job
> Managers|https://cwiki.apache.org/confluence/display/FLINK/FLIP+116%3A+Unified+Memory+Configuration+for+Job+Managers].
> That leaves only {{slotsPerTaskManager}}, which can easily get from the
> configuration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
