[
https://issues.apache.org/jira/browse/FLINK-16734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065281#comment-17065281
]
Xintong Song commented on FLINK-16734:
--------------------------------------
Although this is an internal class, there are users looking into Flink's source
codes and confused by this class.
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/usae-of-ClusterSpecificationBuilder-taskManagerMemoryMB-td33856.html
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ClusterSpecification-and-Configuration-questions-td33857.html
> 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
>
> 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)
