[
https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524112#comment-14524112
]
Hadoop QA commented on YARN-160:
--------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12690562/apache-yarn-160.3.patch
|
| Optional Tests | javac unit findbugs checkstyle javadoc |
| git revision | trunk / d3d019c |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/7579/console |
This message was automatically generated.
> 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)
