[jira] [Commented] (YARN-366) Add a tracing async dispatcher to simplify debugging

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

[jira] [Commented] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617838#comment-13617838 ] Sandy Ryza commented on YARN-366: - Thanks for the review, Vinod. I uploaded a new patch tha

[jira] [Updated] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-366: Attachment: YARN-366-1.patch > Add a tracing async dispatcher to simplify debugging > ---

[jira] [Resolved] (YARN-484) Fair Scheduler preemption fails if the other queue has a mapreduce job with some tasks in excess of cluster capacity

[ https://issues.apache.org/jira/browse/YARN-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-484. - Resolution: Cannot Reproduce > Fair Scheduler preemption fails if the other queue has a mapreduce job w

[jira] [Commented] (YARN-484) Fair Scheduler preemption fails if the other queue has a mapreduce job with some tasks in excess of cluster capacity

[ https://issues.apache.org/jira/browse/YARN-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617743#comment-13617743 ] Sandy Ryza commented on YARN-484: - I just tried this out on Apache trunk using your configs

[jira] [Created] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

Sandy Ryza created YARN-521: --- Summary: Augment AM - RM client module to be able to request containers only at specific locations Key: YARN-521 URL: https://issues.apache.org/jira/browse/YARN-521 Project: Ha

[jira] [Commented] (YARN-515) Node Manager not getting the master key

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

[jira] [Commented] (YARN-515) Node Manager not getting the master key

[ https://issues.apache.org/jira/browse/YARN-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617665#comment-13617665 ] Jason Lowe commented on YARN-515: - +1 > Node Manager not getting the master

[jira] [Created] (YARN-520) webservices API ws/v1/cluster/nodes doesn't return LOST nodes

Nathan Roberts created YARN-520: --- Summary: webservices API ws/v1/cluster/nodes doesn't return LOST nodes Key: YARN-520 URL: https://issues.apache.org/jira/browse/YARN-520 Project: Hadoop YARN

[jira] [Commented] (YARN-276) Capacity Scheduler can hang when submit many jobs concurrently

[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617444#comment-13617444 ] Thomas Graves commented on YARN-276: Also note that the am resource percent can be set o

[jira] [Commented] (YARN-515) Node Manager not getting the master key

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

[jira] [Assigned] (YARN-515) Node Manager not getting the master key

[ https://issues.apache.org/jira/browse/YARN-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans reassigned YARN-515: Assignee: Robert Joseph Evans > Node Manager not getting the master key > ---

[jira] [Commented] (YARN-276) Capacity Scheduler can hang when submit many jobs concurrently

[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617403#comment-13617403 ] Thomas Graves commented on YARN-276: I agree with Zhijie on this, if we are changing it

[jira] [Updated] (YARN-515) Node Manager not getting the master key

[ https://issues.apache.org/jira/browse/YARN-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated YARN-515: - Attachment: YARN-515.txt This should fix the issue. We forgot to tell the wrapper to rebui

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

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

[jira] [Commented] (YARN-515) Node Manager not getting the master key

[ https://issues.apache.org/jira/browse/YARN-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617379#comment-13617379 ] Robert Joseph Evans commented on YARN-515: -- Yes the issue is that there is a rebuil

[jira] [Commented] (YARN-515) Node Manager not getting the master key

[ https://issues.apache.org/jira/browse/YARN-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617373#comment-13617373 ] Robert Joseph Evans commented on YARN-515: -- This issue appears to be cause by a bug

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

[ https://issues.apache.org/jira/browse/YARN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617367#comment-13617367 ] Robert Joseph Evans commented on YARN-112: -- Vinod, I just glanced at the latest pa

[jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable

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

[jira] [Commented] (YARN-496) Fair scheduler configs are refreshed inconsistently in reinitialize

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

[jira] [Commented] (YARN-209) Capacity scheduler doesn't trigger app-activation after adding nodes

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

[jira] [Commented] (YARN-450) Define value for * in the scheduling protocol

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

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

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

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617340#comment-13617340 ] Arun C Murthy commented on YARN-460: +1, thanks Tom! > CS user left in

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617337#comment-13617337 ] Thomas Graves commented on YARN-460: filed YARN-519 to follow up with the error handling

[jira] [Created] (YARN-519) Investigate adding a more generic error field to AMResponse

Thomas Graves created YARN-519: -- Summary: Investigate adding a more generic error field to AMResponse Key: YARN-519 URL: https://issues.apache.org/jira/browse/YARN-519 Project: Hadoop YARN Issu

[jira] [Updated] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-460: --- Attachment: YARN-460.patch trunk patch. After thinking about this more and talking to Arun a bit about

[jira] [Updated] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-460: --- Attachment: YARN-460-branch-0.23.patch branch-23 patch with just the stopped check. >

[jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable

[ https://issues.apache.org/jira/browse/YARN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617312#comment-13617312 ] Hudson commented on YARN-24: Integrated in Hadoop-Hdfs-trunk #1358 (See [https://builds.apache.o

[jira] [Commented] (YARN-496) Fair scheduler configs are refreshed inconsistently in reinitialize

[ https://issues.apache.org/jira/browse/YARN-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617308#comment-13617308 ] Hudson commented on YARN-496: - Integrated in Hadoop-Hdfs-trunk #1358 (See [https://builds.apach

[jira] [Commented] (YARN-450) Define value for * in the scheduling protocol

[ https://issues.apache.org/jira/browse/YARN-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617305#comment-13617305 ] Hudson commented on YARN-450: - Integrated in Hadoop-Hdfs-trunk #1358 (See [https://builds.apach

[jira] [Commented] (YARN-209) Capacity scheduler doesn't trigger app-activation after adding nodes

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617304#comment-13617304 ] Hudson commented on YARN-209: - Integrated in Hadoop-Hdfs-trunk #1358 (See [https://builds.apach

[jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable

[ https://issues.apache.org/jira/browse/YARN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617236#comment-13617236 ] Hudson commented on YARN-24: Integrated in Hadoop-Yarn-trunk #169 (See [https://builds.apache.or

[jira] [Commented] (YARN-496) Fair scheduler configs are refreshed inconsistently in reinitialize

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

[jira] [Commented] (YARN-450) Define value for * in the scheduling protocol

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

[jira] [Commented] (YARN-209) Capacity scheduler doesn't trigger app-activation after adding nodes

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

[jira] [Created] (YARN-518) Fair Scheduler's document link could be added to the hadoop 2.x main doc page

Dapeng Sun created YARN-518: --- Summary: Fair Scheduler's document link could be added to the hadoop 2.x main doc page Key: YARN-518 URL: https://issues.apache.org/jira/browse/YARN-518 Project: Hadoop YARN

[jira] [Moved] (YARN-517) Document Yarn/MR2 performance related configurations and how to tune them.

[ https://issues.apache.org/jira/browse/YARN-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du moved MAPREDUCE-4364 to YARN-517: Component/s: (was: documentation) documentation