[
https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523921#comment-14523921
]
Vinod Kumar Vavilapalli commented on YARN-160:
----------------------------------------------
bq. Junping felt we should add it to cover upgrade scenarios. What do you think?
Okay, not sure of the upgrade issue, but I think it makes sense to have an
explicit flag.
bq. I think resource.percentage-pmem-limit should be analogous to
resource.percentage-physical-cpu-limit in that it sets the limit as a
percentage of total memory. What about something like
"yarn.nodemanager.default-percentage-pmem-limit"?
Don't quite understand your comment. We can have a
resource.percentage-pmem-limit and say that this only works when
hardware-detection is enabled?
> nodemanagers should obtain cpu/memory values from underlying OS
> ---------------------------------------------------------------
>
> Key: YARN-160
> URL: https://issues.apache.org/jira/browse/YARN-160
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Affects Versions: 2.0.3-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Varun Vasudev
> Attachments: apache-yarn-160.0.patch, apache-yarn-160.1.patch,
> apache-yarn-160.2.patch, apache-yarn-160.3.patch
>
>
> As mentioned in YARN-2
> *NM memory and CPU configs*
> Currently these values are coming from the config of the NM, we should be
> able to obtain those values from the OS (ie, in the case of Linux from
> /proc/meminfo & /proc/cpuinfo). As this is highly OS dependent we should have
> an interface that obtains this information. In addition implementations of
> this interface should be able to specify a mem/cpu offset (amount of mem/cpu
> not to be avail as YARN resource), this would allow to reserve mem/cpu for
> the OS and other services outside of YARN containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
