Hadoop YARN
  1. Hadoop YARN
  2. YARN-460

CS user left in list of active users for the queue even when application finished

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.23.7, 2.0.4-alpha
    • Fix Version/s: 0.23.7, 2.1.0-beta
    • Component/s: capacityscheduler
    • Labels:
      None

      Description

      We have seen a user get left in the queues list of active users even though the application was removed. This can cause everyone else in the queue to get less resources if using the minimum user limit percent config.

      1. YARN-460-branch-0.23.patch
        3 kB
        Thomas Graves
      2. YARN-460-branch-0.23.patch
        8 kB
        Thomas Graves
      3. YARN-460-branch-0.23.patch
        4 kB
        Thomas Graves
      4. YARN-460.patch
        3 kB
        Thomas Graves
      5. YARN-460.patch
        3 kB
        Thomas Graves
      6. YARN-460.patch
        8 kB
        Thomas Graves
      7. YARN-460.patch
        4 kB
        Thomas Graves

        Activity

        Hide
        Thomas Graves added a comment -

        We think this might be a race between when the application gets removed (LeafQueue.removeApplication) and between a possibly in flight allocate call from the AM. If LeafQueue.removeApplication is called it removes the user from the list of active users. If a CapacityScheduler.allocate call comes in before the application gets removed from application datastructures in CapacityScheduler.doneApplication, it could add it back to the activeUser list because the allocate() call just checks to make sure application isn't null. We either need to make the check in allocate better or prevent the race between finish and removing.

        This is basically in CapacityScheduler.doneApplication:
        } else

        { queue.finishApplication(application, queue.getQueueName()); }

        // Remove from our data-structure
        applications.remove(applicationAttemptId);

        Show
        Thomas Graves added a comment - We think this might be a race between when the application gets removed (LeafQueue.removeApplication) and between a possibly in flight allocate call from the AM. If LeafQueue.removeApplication is called it removes the user from the list of active users. If a CapacityScheduler.allocate call comes in before the application gets removed from application datastructures in CapacityScheduler.doneApplication, it could add it back to the activeUser list because the allocate() call just checks to make sure application isn't null. We either need to make the check in allocate better or prevent the race between finish and removing. This is basically in CapacityScheduler.doneApplication: } else { queue.finishApplication(application, queue.getQueueName()); } // Remove from our data-structure applications.remove(applicationAttemptId);
        Hide
        Thomas Graves added a comment -

        Just for reference the RM log shows the application removed:
        2013-02-27 06:59:50,390 [ResourceManager Event Processor] INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: Application removed - appId: application_1360172387725_270658 user: userfoo queue: adhoc #user-pending-applications: 0 #user-active-applications: 5 #queue-pending-applications: 0 #queue-active-applications: 25

        Unfortunately the allocate call only logs at DEBUG level and we are at INFO level.

        Show
        Thomas Graves added a comment - Just for reference the RM log shows the application removed: 2013-02-27 06:59:50,390 [ResourceManager Event Processor] INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: Application removed - appId: application_1360172387725_270658 user: userfoo queue: adhoc #user-pending-applications: 0 #user-active-applications: 5 #queue-pending-applications: 0 #queue-active-applications: 25 Unfortunately the allocate call only logs at DEBUG level and we are at INFO level.
        Hide
        Thomas Graves added a comment -

        Note that this is due to the fact that CapacityScheduler.allocate() call is not synchronized like other calls so the capacity scheduler thread can be calling doneApplication at the same time the allocate call comes in. This means that allocate can be looking at/updating the SchedulerApp while its being stopped. We need a way to either synchronize on the SchdulerApp itself or perhaps have the calls into SchedulerApp check to make sure its hasn't been stopped.

        Show
        Thomas Graves added a comment - Note that this is due to the fact that CapacityScheduler.allocate() call is not synchronized like other calls so the capacity scheduler thread can be calling doneApplication at the same time the allocate call comes in. This means that allocate can be looking at/updating the SchedulerApp while its being stopped. We need a way to either synchronize on the SchdulerApp itself or perhaps have the calls into SchedulerApp check to make sure its hasn't been stopped.
        Hide
        Thomas Graves added a comment -

        So I think we can simply track if the application gets stopped and then check that in the allocate() call before really processing it.

        All the stopping/removing of the application happens in CS.doneApplication and the race is really between the calls in that function and the fact that allocate() isn't synchronized. No other paths I could find should cause issues since most of the other funtions in CS are all synchronized and wouldn't run while the doneApplication is happening.

        here is a preliminary patch that I am going to do some more testing on it. The checks for stopped in the SchedulerApp are extra I was just being paranoid.

        Show
        Thomas Graves added a comment - So I think we can simply track if the application gets stopped and then check that in the allocate() call before really processing it. All the stopping/removing of the application happens in CS.doneApplication and the race is really between the calls in that function and the fact that allocate() isn't synchronized. No other paths I could find should cause issues since most of the other funtions in CS are all synchronized and wouldn't run while the doneApplication is happening. here is a preliminary patch that I am going to do some more testing on it. The checks for stopped in the SchedulerApp are extra I was just being paranoid.
        Hide
        Thomas Graves added a comment -

        Note that is the branch-0.23 patch. Working on trunk/branch-2 as it as renamed FicaSchedulerApp

        Show
        Thomas Graves added a comment - Note that is the branch-0.23 patch. Working on trunk/branch-2 as it as renamed FicaSchedulerApp
        Hide
        Thomas Graves added a comment -

        updated patch for trunk/branch-2.

        Show
        Thomas Graves added a comment - updated patch for trunk/branch-2.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12572846/YARN-460.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/484//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/484//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12572846/YARN-460.patch against trunk revision . +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/484//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/484//console This message is automatically generated.
        Hide
        Arun C Murthy added a comment -

        Thomas - one thing that bothers me...

        Should we return some sort of error indication back to the AM in the case that it has been 'stopped'?

        Currently your patch just returns EMPTY_ALLOCATION... OTOH, the current usage of EMPTY_ALLOCATION i.e. when Application is 'null' also suffers from same issue i.e. no error indication to AM.

        Show
        Arun C Murthy added a comment - Thomas - one thing that bothers me... Should we return some sort of error indication back to the AM in the case that it has been 'stopped'? Currently your patch just returns EMPTY_ALLOCATION... OTOH, the current usage of EMPTY_ALLOCATION i.e. when Application is 'null' also suffers from same issue i.e. no error indication to AM.
        Hide
        Arun C Murthy added a comment -

        How about adding a 'error' or 'stopped' boolean or some indication to AM in the Allocation struct?

        Show
        Arun C Murthy added a comment - How about adding a 'error' or 'stopped' boolean or some indication to AM in the Allocation struct?
        Hide
        Thomas Graves added a comment -

        Yeah I think that is a good idea. Perhaps something in the AMResponse. It might be nice if we could include a description of the problem as well, I'll look at it more to see what I can come up with.

        Show
        Thomas Graves added a comment - Yeah I think that is a good idea. Perhaps something in the AMResponse. It might be nice if we could include a description of the problem as well, I'll look at it more to see what I can come up with.
        Hide
        Thomas Graves added a comment -

        updated branch-0.23 patch having Allocation return an error and then ApplicationMasterService send reboot command to AM.

        Show
        Thomas Graves added a comment - updated branch-0.23 patch having Allocation return an error and then ApplicationMasterService send reboot command to AM.
        Hide
        Thomas Graves added a comment -

        trunk and branch-2 patch. Unfortunately I couldn't easily come up with a unit test to hit the application stopped condition (without hitting the null check) due to the data structures being private.

        Show
        Thomas Graves added a comment - trunk and branch-2 patch. Unfortunately I couldn't easily come up with a unit test to hit the application stopped condition (without hitting the null check) due to the data structures being private.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12573361/YARN-460.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        -1 eclipse:eclipse. The patch failed to build with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/506//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/506//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12573361/YARN-460.patch against trunk revision . +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. -1 eclipse:eclipse . The patch failed to build with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/506//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/506//console This message is automatically generated.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12573361/YARN-460.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/507//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/507//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12573361/YARN-460.patch against trunk revision . +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/507//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/507//console This message is automatically generated.
        Hide
        Thomas Graves added a comment -

        Also note that I manually tested this by delaying the kill container message going to AM and sleeping between when the app is marked done and before it was removed from the application list. I was able to reproduce the issue, then saw this patch fix it and the AM get the reboot command. I tested both capacity scheduler and fifo.

        Show
        Thomas Graves added a comment - Also note that I manually tested this by delaying the kill container message going to AM and sleeping between when the app is marked done and before it was removed from the application list. I was able to reproduce the issue, then saw this patch fix it and the AM get the reboot command. I tested both capacity scheduler and fifo.
        Hide
        Thomas Graves added a comment -

        branch-23 patch with just the stopped check.

        Show
        Thomas Graves added a comment - branch-23 patch with just the stopped check.
        Hide
        Thomas Graves added a comment -

        trunk patch. After thinking about this more and talking to Arun a bit about it. I have made this patch just contain the check for stopped and it returns an EMPTY_ALLOCATION similar to what it did before if the application was null when calling allocate(). I will file a follow up jira to investigate if the AMResponse should have another field so that the RM could send the AM useful error information other then just reboot.

        Show
        Thomas Graves added a comment - trunk patch. After thinking about this more and talking to Arun a bit about it. I have made this patch just contain the check for stopped and it returns an EMPTY_ALLOCATION similar to what it did before if the application was null when calling allocate(). I will file a follow up jira to investigate if the AMResponse should have another field so that the RM could send the AM useful error information other then just reboot.
        Hide
        Thomas Graves added a comment -

        filed YARN-519 to follow up with the error handling.

        Show
        Thomas Graves added a comment - filed YARN-519 to follow up with the error handling.
        Hide
        Arun C Murthy added a comment -

        +1, thanks Tom!

        Show
        Arun C Murthy added a comment - +1, thanks Tom!
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12576068/YARN-460.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/628//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/628//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12576068/YARN-460.patch against trunk revision . +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/628//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/628//console This message is automatically generated.
        Hide
        Hudson added a comment -

        Integrated in Hadoop-trunk-Commit #3539 (See https://builds.apache.org/job/Hadoop-trunk-Commit/3539/)
        YARN-460. CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462486)

        Result = SUCCESS
        tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486
        Files :

        • /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Show
        Hudson added a comment - Integrated in Hadoop-trunk-Commit #3539 (See https://builds.apache.org/job/Hadoop-trunk-Commit/3539/ ) YARN-460 . CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462486) Result = SUCCESS tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486 Files : /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Hide
        Thomas Graves added a comment -

        Thanks Arun! I committed this.

        Show
        Thomas Graves added a comment - Thanks Arun! I committed this.
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Yarn-trunk #170 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/170/)
        YARN-460. CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462486)

        Result = FAILURE
        tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486
        Files :

        • /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Show
        Hudson added a comment - Integrated in Hadoop-Yarn-trunk #170 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/170/ ) YARN-460 . CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462486) Result = FAILURE tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486 Files : /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Hdfs-0.23-Build #568 (See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/568/)
        YARN-460. CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462497)

        Result = SUCCESS
        tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462497
        Files :

        • /hadoop/common/branches/branch-0.23/hadoop-yarn-project/CHANGES.txt
        • /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerApp.java
        • /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
        • /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Show
        Hudson added a comment - Integrated in Hadoop-Hdfs-0.23-Build #568 (See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/568/ ) YARN-460 . CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462497) Result = SUCCESS tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462497 Files : /hadoop/common/branches/branch-0.23/hadoop-yarn-project/CHANGES.txt /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerApp.java /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java /hadoop/common/branches/branch-0.23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Hdfs-trunk #1359 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1359/)
        YARN-460. CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462486)

        Result = FAILURE
        tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486
        Files :

        • /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Show
        Hudson added a comment - Integrated in Hadoop-Hdfs-trunk #1359 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1359/ ) YARN-460 . CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462486) Result = FAILURE tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486 Files : /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Mapreduce-trunk #1387 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1387/)
        YARN-460. CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462486)

        Result = FAILURE
        tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486
        Files :

        • /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
        Show
        Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk #1387 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1387/ ) YARN-460 . CS user left in list of active users for the queue even when application finished (tgraves) (Revision 1462486) Result = FAILURE tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486 Files : /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java

          People

          • Assignee:
            Thomas Graves
            Reporter:
            Thomas Graves
          • Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development