[jira] [Commented] (YARN-4768) getAvailablePhysicalMemorySize can be inaccurate on linux

[ https://issues.apache.org/jira/browse/YARN-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15279048#comment-15279048 ] Hudson commented on YARN-4768: -- FAILURE: Integrated in Hadoop-trunk-Commit #9741 (See

[jira] [Commented] (YARN-4768) getAvailablePhysicalMemorySize can be inaccurate on linux

[ https://issues.apache.org/jira/browse/YARN-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278366#comment-15278366 ] Eric Payne commented on YARN-4768: -- The fix LGTM. +1 > getAvailablePhysicalMemorySize can be inaccurate

[jira] [Commented] (YARN-4768) getAvailablePhysicalMemorySize can be inaccurate on linux

[ https://issues.apache.org/jira/browse/YARN-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15276849#comment-15276849 ] Eric Payne commented on YARN-4768: -- bq. "Inactive(file)" would seem more accurate but it's not available

[jira] [Commented] (YARN-4768) getAvailablePhysicalMemorySize can be inaccurate on linux

[ https://issues.apache.org/jira/browse/YARN-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199732#comment-15199732 ] Nathan Roberts commented on YARN-4768: -- Any comments on this approach? >

[jira] [Commented] (YARN-4768) getAvailablePhysicalMemorySize can be inaccurate on linux

[ https://issues.apache.org/jira/browse/YARN-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185229#comment-15185229 ] Hadoop QA commented on YARN-4768: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||