[
https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337589#comment-15337589
]
Karthik Kambatla commented on YARN-5270:
----------------------------------------
YARN-5077 has been fixed to use the right version of getMemory, so that is no
longer an issue.
My primary request is to remove any ambiguity for users of the Resource API as
it is at the core of a lot interaction with Yarn and within Yarn. The two
sources of ambiguity are:
# getMemory vs getMemorySize: One is deprecated and other is unstable. If we
are deprecating a stable API, I think we should provide another stable API. I
am comfortable with making getMemorySize stable, if we are comfortable with the
name.
# getVirtualCores vs getVirtualCoresSize: Which of the two methods do we expect
users to use? Also, if we do not anticipate this to be a problem, can we avoid
changing this now? At the very least, we could avoid adding the getter so there
is no ambiguity on which method to use.
Can we also fix the issue where Resources casts long to int?
> Solve miscellaneous issues caused by YARN-4844
> ----------------------------------------------
>
> Key: YARN-5270
> URL: https://issues.apache.org/jira/browse/YARN-5270
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
>
> Such as javac warnings reported by YARN-5077 and type converting issues in
> Resources class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
