[jira] [Commented] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

[ https://issues.apache.org/jira/browse/YARN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868733#comment-13868733 ] Hudson commented on YARN-1166: -- FAILURE: Integrated in Hadoop-Yarn-trunk #449 (See

[jira] [Commented] (YARN-1566) Change distributed-shell to retain containers from previous AppAttempt

[ https://issues.apache.org/jira/browse/YARN-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868730#comment-13868730 ] Hudson commented on YARN-1566: -- FAILURE: Integrated in Hadoop-Yarn-trunk #449 (See

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868726#comment-13868726 ] Hudson commented on YARN-1033: -- FAILURE: Integrated in Hadoop-Yarn-trunk #449 (See

[jira] [Commented] (YARN-1574) RMDispatcher should be reset on transition to standby

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868732#comment-13868732 ] Hudson commented on YARN-1574: -- FAILURE: Integrated in Hadoop-Yarn-trunk #449 (See

[jira] [Commented] (YARN-1041) Protocol changes for RM to bind and notify a restarted AM of existing containers

[ https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868731#comment-13868731 ] Hudson commented on YARN-1041: -- FAILURE: Integrated in Hadoop-Yarn-trunk #449 (See

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868739#comment-13868739 ] Steve Loughran commented on YARN-888: - +1 to the don't add dependencies here comment

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868768#comment-13868768 ] Hudson commented on YARN-1033: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1666 (See

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868770#comment-13868770 ] Hudson commented on YARN-1490: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1666 (See

[jira] [Commented] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

[ https://issues.apache.org/jira/browse/YARN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868785#comment-13868785 ] Hudson commented on YARN-1166: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1641 (See

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868778#comment-13868778 ] Hudson commented on YARN-1033: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1641 (See

[jira] [Commented] (YARN-1566) Change distributed-shell to retain containers from previous AppAttempt

[ https://issues.apache.org/jira/browse/YARN-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868782#comment-13868782 ] Hudson commented on YARN-1566: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1641 (See

[jira] [Updated] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1567: - Attachment: YARN-1567-3.patch In Fair Scheduler, allow empty queues to change between leaf and parent on

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868875#comment-13868875 ] Sandy Ryza commented on YARN-1567: -- Test failure is unrelated. Fixed findbugs warning.

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

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

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1386#comment-1386 ] Sandy Ryza commented on YARN-1567: -- Test failure is unrelated In Fair Scheduler, allow

[jira] [Commented] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

[ https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868891#comment-13868891 ] Bikas Saha commented on YARN-1489: -- We need to come to a conclusion on how to allow the

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868923#comment-13868923 ] Xuan Gong commented on YARN-1410: - [~bikassaha], [~kkambatl]. Please take a look. Thanks