hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alejandro Abdelnur <tuc...@gmail.com>
Subject Re: [jira] [Commented] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS
Date Mon, 15 Oct 2012 17:51:09 GMT
thanks Radim, unless i'm missing something this is not wired, correct? yes being able to override
makes sense


On Oct 15, 2012, at 10:36 AM, "Radim Kolar (JIRA)" <jira@apache.org> wrote:

>    [ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476288#comment-13476288
> Radim Kolar commented on YARN-160:
> ----------------------------------
> there is a interface from obtaining these values from OS. Its called resourcecalculator
plugin. It might be good to do autodetection but i need ability to override these values in
>> 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: Alejandro Abdelnur
>>            Fix For: 2.0.3-alpha
>> 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 is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message