[jira] [Updated] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-561: --- Attachment: YARN-561.6.patch fix the test case failure > Nodemanager should set some key infor

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

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

[jira] [Commented] (YARN-591) RM recovery related records do not belong to the API

s of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12579480/YARN-591-20130418.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear t

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636102#comment-13636102 ] Bikas Saha commented on YARN-562: - The name clusterTimeStamp confuses me. What time is it? T

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636095#comment-13636095 ] Xuan Gong commented on YARN-561: Also remove APPLICATION_ATTEMPT_ID_ENV from MapReduceChildJ

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

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

[jira] [Updated] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-561: --- Attachment: YARN-561.5.patch > Nodemanager should set some key information into the environment of every >

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636093#comment-13636093 ] Xuan Gong commented on YARN-561: The new patch includes several changes: 1. move node_http_p

[jira] [Updated] (YARN-591) RM recovery related records do not belong to the API

Reporter: Vinod Kumar Vavilapalli >Assignee: Vinod Kumar Vavilapalli > Attachments: YARN-591-20130418.txt > > > We need to move out AppliationStateData and ApplicationAttemptStateData into > resourcemanager module. They are not part of the public API.. -- This

[jira] [Updated] (YARN-591) RM recovery related records do not belong to the API

[ https://issues.apache.org/jira/browse/YARN-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-591: - Attachment: YARN-591-20130418.txt Simple patch moving records out into

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636077#comment-13636077 ] Bikas Saha commented on YARN-392: - bq. would it not make sense to go with the convention use

[jira] [Updated] (YARN-71) Ensure/confirm that the NodeManager cleans up local-dirs on restart

[ https://issues.apache.org/jira/browse/YARN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-71: --- Fix Version/s: 0.23.8 Thanks, Xuan. I committed this to branch-0.23 as well. > Ensure/confirm

[jira] [Created] (YARN-591) RM recovery related records do not belong to the API

Vinod Kumar Vavilapalli created YARN-591: Summary: RM recovery related records do not belong to the API Key: YARN-591 URL: https://issues.apache.org/jira/browse/YARN-591 Project: Hadoop YARN

[jira] [Updated] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-562: - Attachment: YARN-562.6.patch new patch fix conflicts with YARN-493, and updated based on last comments

[jira] [Commented] (YARN-547) Race condition in Public / Private Localizer may result into resource getting downloaded again

s of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12579471/yarn-547-20130418.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to inc

[jira] [Commented] (YARN-576) RM should not allow registrations from NMs that do not satisfy minimum scheduler allocations

[ https://issues.apache.org/jira/browse/YARN-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635978#comment-13635978 ] Vinod Kumar Vavilapalli commented on YARN-576: -- Kenji, the patch looks good to

[jira] [Created] (YARN-590) Add an optional mesage to RegisterNodeManagerResponse as to why NM is being asked to resync or shutdown

Vinod Kumar Vavilapalli created YARN-590: Summary: Add an optional mesage to RegisterNodeManagerResponse as to why NM is being asked to resync or shutdown Key: YARN-590 URL: https://issues.apache.org/jira/

[jira] [Updated] (YARN-547) Race condition in Public / Private Localizer may result into resource getting downloaded again

[ https://issues.apache.org/jira/browse/YARN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-547: --- Attachment: yarn-547-20130418.patch > Race condition in Public / Private Localizer

[jira] [Assigned] (YARN-576) RM should not allow registrations from NMs that do not satisfy minimum scheduler allocations

[ https://issues.apache.org/jira/browse/YARN-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-576: Assignee: Kenji Kikushima > RM should not allow registrations from NMs th

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

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

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

[ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635949#comment-13635949 ] Vinod Kumar Vavilapalli commented on YARN-493: -- okay, you win. My only gripe i

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

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

[jira] [Commented] (YARN-289) Fair scheduler doesn't satisfy smaller request when bigger one is outstanding

[ https://issues.apache.org/jira/browse/YARN-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635937#comment-13635937 ] Sandy Ryza commented on YARN-289: - Yeah, that appears to be the problem. >

[jira] [Created] (YARN-589) Expose a REST API for monitoring the fair scheduler

Sandy Ryza created YARN-589: --- Summary: Expose a REST API for monitoring the fair scheduler Key: YARN-589 URL: https://issues.apache.org/jira/browse/YARN-589 Project: Hadoop YARN Issue Type: Improve

[jira] [Resolved] (YARN-215) Allow app's queue to be changed through fair scheduler web UI

[ https://issues.apache.org/jira/browse/YARN-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-215. - Resolution: Won't Fix Allowing this through the web UI presents too many security issues. This should be

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

[ https://issues.apache.org/jira/browse/YARN-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635910#comment-13635910 ] Vinod Kumar Vavilapalli commented on YARN-441: -- Latest patch loos good, +1, che

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

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

[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application

[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635837#comment-13635837 ] Alejandro Abdelnur commented on YARN-333: - In case is not clear, I favor #B

[jira] [Created] (YARN-588) Two identical utility methods in different classes to build Resource

Sandy Ryza created YARN-588: --- Summary: Two identical utility methods in different classes to build Resource Key: YARN-588 URL: https://issues.apache.org/jira/browse/YARN-588 Project: Hadoop YARN I

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

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

[jira] [Updated] (YARN-476) ProcfsBasedProcessTree info message confuses users

[ https://issues.apache.org/jira/browse/YARN-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-476: Fix Version/s: 0.23.8 Thanks, Sandy. I also committed this to branch-0.23. > ProcfsBasedPro

[jira] [Updated] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-562: - Attachment: YARN-562.5.patch New patch fix conflicts with MAPREDUCE-5152 > NM should reject contai

[jira] [Updated] (YARN-441) Clean up unused collection methods in various APIs

[ https://issues.apache.org/jira/browse/YARN-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-441: --- Attachment: YARN-441.9.patch fix -1 on javaDoc warning > Clean up unused collection methods in

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

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

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

[ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635698#comment-13635698 ] Chris Nauroth commented on YARN-493: The conclusion of YARN-359 was to promote those met

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

[ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635688#comment-13635688 ] Vinod Kumar Vavilapalli commented on YARN-493: -- The patch looks good to me. One

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

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

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

[ https://issues.apache.org/jira/browse/YARN-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635680#comment-13635680 ] Xuan Gong commented on YARN-441: 1.Apply the latest comments. 2.Pass all yarn tests locally

[jira] [Updated] (YARN-441) Clean up unused collection methods in various APIs

[ https://issues.apache.org/jira/browse/YARN-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-441: --- Attachment: YARN-441.8.patch > Clean up unused collection methods in various APIs > ---

[jira] [Updated] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-2.patch > Make it possible to schedule to specific nodes without dropping locality >

[jira] [Updated] (YARN-571) User should not be part of ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-571: - Attachment: YARN-571-20130418.txt Patch updated against latest trunk, ready for

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

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

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635643#comment-13635643 ] Sandy Ryza commented on YARN-392: - Uploaded a patch that adds a test for strict locality in

[jira] [Updated] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-2.patch > Make it possible to schedule to specific nodes without dropping locality >

[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application

[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635606#comment-13635606 ] Alejandro Abdelnur commented on YARN-333: - Stepping back a bit. In Hadoop 1, using

[jira] [Commented] (YARN-585) TestFairScheduler#testNotAllowSubmitApplication is broken due to YARN-514

[ https://issues.apache.org/jira/browse/YARN-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635547#comment-13635547 ] Zhijie Shen commented on YARN-585: -- I stepped through the test, and found addapplication wo

[jira] [Commented] (YARN-585) TestFairScheduler#testNotAllowSubmitApplication is broken due to YARN-514

[ https://issues.apache.org/jira/browse/YARN-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635492#comment-13635492 ] Karthik Kambatla commented on YARN-585: --- Agree with Bikas, +1 on fixing the test furth

[jira] [Created] (YARN-587) Rewrite TestFairScheduler#testNotAllowSubmitApplication to not bypass RM state machine

Karthik Kambatla created YARN-587: - Summary: Rewrite TestFairScheduler#testNotAllowSubmitApplication to not bypass RM state machine Key: YARN-587 URL: https://issues.apache.org/jira/browse/YARN-587 Pr

[jira] [Commented] (YARN-482) FS: Extend SchedulingMode to intermediate queues

[ https://issues.apache.org/jira/browse/YARN-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635485#comment-13635485 ] Karthik Kambatla commented on YARN-482: --- Thanks for taking care of this, Alejandro.

[jira] [Commented] (YARN-482) FS: Extend SchedulingMode to intermediate queues

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

[jira] [Commented] (YARN-585) TestFairScheduler#testNotAllowSubmitApplication is broken due to YARN-514

[ https://issues.apache.org/jira/browse/YARN-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635454#comment-13635454 ] Bikas Saha commented on YARN-585: - It looks like the test is completely bypassing the state

[jira] [Commented] (YARN-482) FS: Extend SchedulingMode to intermediate queues

[ https://issues.apache.org/jira/browse/YARN-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635452#comment-13635452 ] Alejandro Abdelnur commented on YARN-482: - I've given the patch a new spin after YAR

[jira] [Commented] (YARN-585) TestFairScheduler#testNotAllowSubmitApplication is broken due to YARN-514

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

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

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

[jira] [Resolved] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-514. -- Resolution: Fixed Fix Version/s: 2.0.5-beta Hadoop Flags: Reviewed I

[jira] [Commented] (YARN-585) TestFairScheduler#testNotAllowSubmitApplication is broken due to YARN-514

[ https://issues.apache.org/jira/browse/YARN-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635403#comment-13635403 ] Vinod Kumar Vavilapalli commented on YARN-585: -- The latest patch looks good to

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

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

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

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

[jira] [Commented] (YARN-476) ProcfsBasedProcessTree info message confuses users

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

[jira] [Assigned] (YARN-586) Typo in ApplicationSubmissionContext#setApplicationId

[ https://issues.apache.org/jira/browse/YARN-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash reassigned YARN-586: - Assignee: Ravi Prakash (was: Zhijie Shen) > Typo in ApplicationSubmissionContext#setApplicatio

[jira] [Updated] (YARN-586) Typo in ApplicationSubmissionContext#setApplicationId

[ https://issues.apache.org/jira/browse/YARN-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-586: -- Assignee: Zhijie Shen (was: Ravi Prakash) > Typo in ApplicationSubmissionContext#setApplicationId >

[jira] [Commented] (YARN-476) ProcfsBasedProcessTree info message confuses users

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

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

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

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

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

[jira] [Commented] (YARN-72) NM should handle cleaning up containers when it shuts down

[ https://issues.apache.org/jira/browse/YARN-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635125#comment-13635125 ] Hudson commented on YARN-72: Integrated in Hadoop-Hdfs-0.23-Build #585 (See [https://builds.apac

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

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

[jira] [Commented] (YARN-476) ProcfsBasedProcessTree info message confuses users

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

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

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

[jira] [Commented] (YARN-585) TestFairScheduler#testNotAllowSubmitApplication is broken due to YARN-514

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

[jira] [Updated] (YARN-126) yarn rmadmin help message contains reference to hadoop cli and JT

[ https://issues.apache.org/jira/browse/YARN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rémy SAISSY updated YARN-126: - Attachment: (was: YARN-126.patch) > yarn rmadmin help message contains reference to hadoop cli and

[jira] [Updated] (YARN-126) yarn rmadmin help message contains reference to hadoop cli and JT

[ https://issues.apache.org/jira/browse/YARN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rémy SAISSY updated YARN-126: - Attachment: (was: YARN-126.patch) > yarn rmadmin help message contains reference to hadoop cli and

[jira] [Commented] (YARN-586) Typo in ApplicationSubmissionContext#setApplicationId

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

[jira] [Updated] (YARN-585) TestFairScheduler#testNotAllowSubmitApplication is broken due to YARN-514

[ https://issues.apache.org/jira/browse/YARN-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-585: - Attachment: YARN-585.2.patch Hi Karthik, the suggestion sounds good. I've modified the patch accordingly.