[
https://issues.apache.org/jira/browse/YARN-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279048#comment-15279048
]
Hudson commented on YARN-4768:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9741 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9741/])
YARN-4768. getAvailablePhysicalMemorySize can be inaccurate on linux. (epayne:
rev 6b1c1cb01cbf979f46cd3ea9308b7745c5595b4f)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/SysInfoLinux.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestSysInfoLinux.java
> getAvailablePhysicalMemorySize can be inaccurate on linux
> ---------------------------------------------------------
>
> Key: YARN-4768
> URL: https://issues.apache.org/jira/browse/YARN-4768
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.0.0, 2.7.2
> Environment: Linux
> Reporter: Nathan Roberts
> Assignee: Nathan Roberts
> Fix For: 2.8.0
>
> Attachments: YARN-4768.patch
>
>
> Algorithm currently uses "MemFree" + "Inactive" from /proc/meminfo
> "Inactive" may not be a very good indication of how much memory can be
> readily freed because it contains both:
> - Pages mapped with MAP_SHARED|MAP_ANONYMOUS (regardless of whether they're
> being actively accessed or not. Unclear to me why this is the case...)
> - Pages mapped MAP_PRIVATE|MAP_ANONYMOUS that have not been accessed recently
> Both of these types of pages probably shouldn't be considered "Available".
> "Inactive(file)" would seem more accurate but it's not available in all
> kernel versions. To keep things simple, maybe just use "Inactive(file)" if
> available, otherwise fallback to "Inactive".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
