[jira] [Updated] (YARN-365) Each NM heartbeat should not generate an event for the Scheduler

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-365: --- Attachment: YARN-365.7.patch > Each NM heartbeat should not generate an event for the Scheduler > -

[jira] [Updated] (YARN-399) Add an out of band heartbeat damper

[ https://issues.apache.org/jira/browse/YARN-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-399: --- Attachment: YARN-399.PATCH patch that I started. Hasn't been tested, attaching for now and will get bac

[jira] [Commented] (YARN-236) RM should point tracking URL to RM web page when app fails to start

[ https://issues.apache.org/jira/browse/YARN-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582515#comment-13582515 ] Hudson commented on YARN-236: - Integrated in Hadoop-trunk-Commit #3368 (See [https://builds.apa

[jira] [Commented] (YARN-236) RM should point tracking URL to RM web page when app fails to start

[ https://issues.apache.org/jira/browse/YARN-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582482#comment-13582482 ] Jonathan Eagles commented on YARN-236: -- +1. Verified this condition still exists and pa

[jira] [Updated] (YARN-100) container-executor should deal with stdout, stderr better

[ https://issues.apache.org/jira/browse/YARN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-100: - Labels: (was: usability) > container-executor should deal with stdout, stderr better > --

[jira] [Updated] (YARN-100) container-executor should deal with stdout, stderr better

[ https://issues.apache.org/jira/browse/YARN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-100: - Labels: usability (was: ) > container-executor should deal with stdout, stderr better > --

[jira] [Resolved] (YARN-130) Yarn examples use wrong configuration

[ https://issues.apache.org/jira/browse/YARN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-130. -- Resolution: Fixed Closing this out as this was addressed as part of YARN-277. > Yarn exa

[jira] [Commented] (YARN-400) RM can return null application resource usage report leading to NPE in client

[ https://issues.apache.org/jira/browse/YARN-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582256#comment-13582256 ] Hudson commented on YARN-400: - Integrated in Hadoop-trunk-Commit #3366 (See [https://builds.apa

[jira] [Commented] (YARN-400) RM can return null application resource usage report leading to NPE in client

[ https://issues.apache.org/jira/browse/YARN-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582247#comment-13582247 ] Thomas Graves commented on YARN-400: +1 Thanks Jason! > RM can return n

[jira] [Commented] (YARN-400) RM can return null application resource usage report leading to NPE in client

[ https://issues.apache.org/jira/browse/YARN-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582242#comment-13582242 ] Hadoop QA commented on YARN-400: {color:red}-1 overall{color}. Here are the results of test

[jira] [Updated] (YARN-400) RM can return null application resource usage report leading to NPE in client

[ https://issues.apache.org/jira/browse/YARN-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-400: Attachment: YARN-400-branch-0.23.patch Thanks for the review, Tom. Here's the patch for branch-0.23.