[jira] [Commented] (YARN-355) RM app submission jams under load

[ https://issues.apache.org/jira/browse/YARN-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573425#comment-13573425 ] Hudson commented on YARN-355: - Integrated in Hadoop-Hdfs-0.23-Build #518 (See

[jira] [Commented] (YARN-150) AppRejectedTransition does not unregister app from master service and scheduler

[ https://issues.apache.org/jira/browse/YARN-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573426#comment-13573426 ] Hudson commented on YARN-150: - Integrated in Hadoop-Hdfs-0.23-Build #518 (See

[jira] [Commented] (YARN-83) Change package of YarnClient to include apache

[ https://issues.apache.org/jira/browse/YARN-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573430#comment-13573430 ] Hudson commented on YARN-83: Integrated in Hadoop-Hdfs-0.23-Build #518 (See

[jira] [Commented] (YARN-40) Provide support for missing yarn commands

[ https://issues.apache.org/jira/browse/YARN-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573433#comment-13573433 ] Hudson commented on YARN-40: Integrated in Hadoop-Hdfs-0.23-Build #518 (See

[jira] [Commented] (YARN-355) RM app submission jams under load

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

[jira] [Commented] (YARN-3) Add support for CPU isolation/monitoring of containers

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

[jira] [Commented] (YARN-355) RM app submission jams under load

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

[jira] [Commented] (YARN-357) App submission should not be synchronized

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

[jira] [Commented] (YARN-3) Add support for CPU isolation/monitoring of containers

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

[jira] [Commented] (YARN-142) Change YARN APIs to throw IOException

[ https://issues.apache.org/jira/browse/YARN-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573516#comment-13573516 ] Tom White commented on YARN-142: I think it'd be useful to have the APIs throw IOException

[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-tabpanelfocusedCommentId=13573546#comment-13573546 ] Jason Lowe commented on YARN-236: - Unfortunately YARN-165 only handled the case where the AM

[jira] [Updated] (YARN-388) testContainerKillOnMemoryOverflow is failing

[ https://issues.apache.org/jira/browse/YARN-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-388: Attachment: YARN-388.patch Patch to make the message pattern being checked a bit more lenient on the memory

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

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573592#comment-13573592 ] Thomas Graves commented on YARN-365: Sorry Sid. I missed your comments and a few

[jira] [Commented] (YARN-388) testContainerKillOnMemoryOverflow is failing

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

[jira] [Commented] (YARN-362) Unexpected extra results when using the task attempt table search

[ https://issues.apache.org/jira/browse/YARN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573686#comment-13573686 ] Ravi Prakash commented on YARN-362: --- I manually tested the patch. Looks good to me. +1 :D

[jira] [Commented] (YARN-377) Fix test failure for HADOOP-9252

[ https://issues.apache.org/jira/browse/YARN-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573722#comment-13573722 ] Jason Lowe commented on YARN-377: - Sorry, didn't see this when I filed YARN-388. Any ETA on

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

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573727#comment-13573727 ] Xuan Gong commented on YARN-365: Thanks for the comment. Will add the aggregation part at

[jira] [Commented] (YARN-388) testContainerKillOnMemoryOverflow is failing

[ https://issues.apache.org/jira/browse/YARN-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573813#comment-13573813 ] Chris Nauroth commented on YARN-388: +1 I applied the patch and verified that the test

[jira] [Commented] (YARN-377) Fix test failure for HADOOP-9252

[ https://issues.apache.org/jira/browse/YARN-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573872#comment-13573872 ] Jason Lowe commented on YARN-377: - If the total fix is coming real soon, then no worries

[jira] [Commented] (YARN-385) ResourceRequestPBImpl's toString() is missing location and # containers

[ https://issues.apache.org/jira/browse/YARN-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573881#comment-13573881 ] Siddharth Seth commented on YARN-385: - +1. Trivial change, doesn't require a unit test.

[jira] [Commented] (YARN-383) AMRMClientImpl should handle null rmClient in stop()

[ https://issues.apache.org/jira/browse/YARN-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573880#comment-13573880 ] Siddharth Seth commented on YARN-383: - +1. Trivial change, doesn't require a unit test.

[jira] [Commented] (YARN-383) AMRMClientImpl should handle null rmClient in stop()

[ https://issues.apache.org/jira/browse/YARN-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573894#comment-13573894 ] Hudson commented on YARN-383: - Integrated in Hadoop-trunk-Commit #3340 (See

[jira] [Commented] (YARN-385) ResourceRequestPBImpl's toString() is missing location and # containers

[ https://issues.apache.org/jira/browse/YARN-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573895#comment-13573895 ] Hudson commented on YARN-385: - Integrated in Hadoop-trunk-Commit #3340 (See

[jira] [Commented] (YARN-142) Change YARN APIs to throw IOException

[ https://issues.apache.org/jira/browse/YARN-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573901#comment-13573901 ] Siddharth Seth commented on YARN-142: - bq. and draw attention to the different

[jira] [Updated] (YARN-377) Fix test failure for HADOOP-9252

[ https://issues.apache.org/jira/browse/YARN-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-377: --- Attachment: YARN-377.1.patch This patch updates {{ContainersMonitorImpl}} to stop using the recently

[jira] [Commented] (YARN-377) Fix test failure for HADOOP-9252

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

[jira] [Updated] (YARN-377) Fix test failure for HADOOP-9252

[ https://issues.apache.org/jira/browse/YARN-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-377: --- Attachment: YARN-377.2.patch Thank you, Nicholas. Here is version 2 of the patch, switching to

[jira] [Updated] (YARN-365) Each NM heartbeat should not generate and 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.4.patch 1.In a single scheduler pass, it will handle all update info. 2.For every events

[jira] [Commented] (YARN-377) Fix TestContainersMonitor for HADOOP-9252

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

[jira] [Commented] (YARN-377) Fix TestContainersMonitor for HADOOP-9252

[ https://issues.apache.org/jira/browse/YARN-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574078#comment-13574078 ] Hudson commented on YARN-377: - Integrated in Hadoop-trunk-Commit #3343 (See

[jira] [Assigned] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM.

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-196: -- Assignee: Xuan Gong Nodemanager if started before starting Resource manager is getting

[jira] [Updated] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM.

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-196: --- Attachment: (was: YARN-196.1.patch) Nodemanager if started before starting Resource manager is

[jira] [Updated] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM.

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-196: --- Attachment: YARN-196.1.patch Nodemanager if started before starting Resource manager is getting

[jira] [Reopened] (YARN-149) ZK-based High Availability (HA) for ResourceManager (RM)

[ https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins reopened YARN-149: -- Assignee: (was: Bikas Saha) ZK-based High Availability (HA) for ResourceManager (RM)

[jira] [Commented] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM

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

[jira] [Commented] (YARN-3) Add support for CPU isolation/monitoring of containers

[ https://issues.apache.org/jira/browse/YARN-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574187#comment-13574187 ] Andrew Ferguson commented on YARN-3: [~acmurthy] thanks for the merge Arun!

[jira] [Commented] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574231#comment-13574231 ] Thomas Graves commented on YARN-249: Thanks Ravi, a few comments and minor nits: - can

[jira] [Updated] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM.

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-196: --- Attachment: YARN-196.2.patch Fix the test failure. testNMShutdownForRegistrationFailure will cover this update