Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-2340

NPE thrown when RM restart after queue is STOPPED. There after RM can not recovery application's and remain in standby

    Details

    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      While job is in progress make Queue state as STOPPED and then restart RM

      Observe that standby RM fails to come up as acive throwing below NPE

      2014-07-23 18:43:24,432 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: appattempt_1406116264351_0014_000002 State change from NEW to SUBMITTED
      2014-07-23 18:43:24,433 FATAL org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in handling event type APP_ATTEMPT_ADDED to the scheduler
      java.lang.NullPointerException
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.addApplicationAttempt(CapacityScheduler.java:568)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:916)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:101)
      at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:602)
      at java.lang.Thread.run(Thread.java:662)
      2014-07-23 18:43:24,434 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Exiting, bbye..

      1. 0001-YARN-2340.patch
        3 kB
        Rohith Sharma K S

        Issue Links

          Activity

          Hide
          rohithsharma Rohith Sharma K S added a comment -

          Thanks Nishan Shetty for reporting this issue. I too encountered with similar situation while testing on trunk code and later RM remain in stand by.

          Show
          rohithsharma Rohith Sharma K S added a comment - Thanks Nishan Shetty for reporting this issue. I too encountered with similar situation while testing on trunk code and later RM remain in stand by.
          Hide
          rohithsharma Rohith Sharma K S added a comment -

          Scenario executed

          1. Start Yarn cluster, and submit long running application to Queue to default.Initially, RM1 is active
          2. Stop the queue default in both RM1 and RM2 using -refreshQueue. Queue can be stopped even when application is running, but wont accept new application submissions.
          3. Switch the RM, let RM2 transitionedToActive. But here application recovery fails since queue already stopped. Below logs shows the failure, but RMAppImpl state is updated as FAILED RMAppAttempt remain as null. RM remain in standby
            2014-12-15 11:01:17,813 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Recovering app: application_1418620667348_0001 with 1 attempts and final state = null
            2014-12-15 11:01:17,814 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: Recovering attempt: appattempt_1418620667348_0001_000001 with final state: null
            /////.....
            /////....
            2014-12-15 11:01:17,824 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: Queue root.default is STOPPED. Cannot accept submission of application: application_1418620667348_0001
            2014-12-15 11:01:17,825 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Failed to submit application application_1418620667348_0001 to queue default from user rohith
            org.apache.hadoop.security.AccessControlException: Queue root.default is STOPPED. Cannot accept submission of application: application_1418620667348_0001
            	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.submitApplication(LeafQueue.java:575)
            
            2014-12-15 11:01:17,939 INFO org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService: Registering app attempt : appattempt_1418620667348_0001_000001
            2014-12-15 11:01:17,941 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Updating application application_1418620667348_0001 with final state: FAILED
            
          4. After restart , Final state in RMApp=FAILED and RMAppImpl=null as shown below. RM can not recover the applications, and continuously fails.
            2014-12-15 11:01:41,493 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Recovering app: application_1418620667348_0001 with 1 attempts and final state = FAILED
            2014-12-15 11:01:41,494 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: Recovering attempt: appattempt_1418620667348_0001_000001 with final state: null
            
          Show
          rohithsharma Rohith Sharma K S added a comment - Scenario executed Start Yarn cluster, and submit long running application to Queue to default.Initially, RM1 is active Stop the queue default in both RM1 and RM2 using -refreshQueue. Queue can be stopped even when application is running, but wont accept new application submissions. Switch the RM, let RM2 transitionedToActive. But here application recovery fails since queue already stopped. Below logs shows the failure, but RMAppImpl state is updated as FAILED RMAppAttempt remain as null . RM remain in standby 2014-12-15 11:01:17,813 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Recovering app: application_1418620667348_0001 with 1 attempts and final state = null 2014-12-15 11:01:17,814 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: Recovering attempt: appattempt_1418620667348_0001_000001 with final state: null /////..... /////.... 2014-12-15 11:01:17,824 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: Queue root.default is STOPPED. Cannot accept submission of application: application_1418620667348_0001 2014-12-15 11:01:17,825 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Failed to submit application application_1418620667348_0001 to queue default from user rohith org.apache.hadoop.security.AccessControlException: Queue root.default is STOPPED. Cannot accept submission of application: application_1418620667348_0001 at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.submitApplication(LeafQueue.java:575) 2014-12-15 11:01:17,939 INFO org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService: Registering app attempt : appattempt_1418620667348_0001_000001 2014-12-15 11:01:17,941 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Updating application application_1418620667348_0001 with final state: FAILED After restart , Final state in RMApp=FAILED and RMAppImpl=null as shown below. RM can not recover the applications, and continuously fails. 2014-12-15 11:01:41,493 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Recovering app: application_1418620667348_0001 with 1 attempts and final state = FAILED 2014-12-15 11:01:41,494 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: Recovering attempt: appattempt_1418620667348_0001_000001 with final state: null
          Hide
          rohithsharma Rohith Sharma K S added a comment -

          Some thoughts for fixing this issue either of below 2 are
          1. Straight away invoke KILL event for application if application is submitting into STOPPED queue during recovering applications. KILL event smothly transition RMApp/RMAppAttempt to KILLED state. But throw exception while killing master container since Either NM's were not registered to RM OR "Connection Refused" when NM is down.
          CS#addApplication

             // Submit to the queue
              try {
                queue.submitApplication(applicationId, user, queueName);
              } catch (AccessControlException ace) {
                LOG.info("Failed to submit application " + applicationId + " to queue "
                    + queueName + " from user " + user, ace);
                if (isAppRecovering) {
                  LOG.info("Killing the application " + applicationId);
                  this.rmContext.getDispatcher().getEventHandler()
                      .handle(new RMAppEvent(applicationId, RMAppEventType.KILL));
                } else {
                  this.rmContext.getDispatcher().getEventHandler()
                      .handle(new RMAppRejectedEvent(applicationId, ace.toString()));
                }
                return;
              }
          

          CS#addApplicationAttempt

              SchedulerApplication<FiCaSchedulerApp> application =
                  applications.get(applicationAttemptId.getApplicationId());
              if (application == null && isAttemptRecovering) {
                LOG.info("Attempt is recovering from an application where Queue is stopped."
                    + applicationAttemptId);
                return;
              }
          

          2. Introduce new event type like APP_RECOVERY_FAILED or APP_SCHEDULER_RECOVERY_FAILED and trigger from Scheduler if app is submitted to stopped queue while recovering. Transitions would be like below
          AppAttempt : NEW to LAUNCHED
          App : NEW to ACCEPTED
          App : ACCEPTED to FINAL_SAVING on event APP_RECOVERY_FAILED or APP_SCHEDULER_RECOVERY_FAILED
          AppAttempt : LAUNCHED to FINAL_SAVING
          AppAttempt : FINAL_SAVING to FAILED
          App : FINAL_SAVING to FAILED

          Please give your suggestions/thoughts.

          Show
          rohithsharma Rohith Sharma K S added a comment - Some thoughts for fixing this issue either of below 2 are 1. Straight away invoke KILL event for application if application is submitting into STOPPED queue during recovering applications. KILL event smothly transition RMApp/RMAppAttempt to KILLED state. But throw exception while killing master container since Either NM's were not registered to RM OR "Connection Refused" when NM is down. CS#addApplication // Submit to the queue try { queue.submitApplication(applicationId, user, queueName); } catch (AccessControlException ace) { LOG.info( "Failed to submit application " + applicationId + " to queue " + queueName + " from user " + user, ace); if (isAppRecovering) { LOG.info( "Killing the application " + applicationId); this .rmContext.getDispatcher().getEventHandler() .handle( new RMAppEvent(applicationId, RMAppEventType.KILL)); } else { this .rmContext.getDispatcher().getEventHandler() .handle( new RMAppRejectedEvent(applicationId, ace.toString())); } return ; } CS#addApplicationAttempt SchedulerApplication<FiCaSchedulerApp> application = applications.get(applicationAttemptId.getApplicationId()); if (application == null && isAttemptRecovering) { LOG.info( "Attempt is recovering from an application where Queue is stopped." + applicationAttemptId); return ; } 2. Introduce new event type like APP_RECOVERY_FAILED or APP_SCHEDULER_RECOVERY_FAILED and trigger from Scheduler if app is submitted to stopped queue while recovering. Transitions would be like below AppAttempt : NEW to LAUNCHED App : NEW to ACCEPTED App : ACCEPTED to FINAL_SAVING on event APP_RECOVERY_FAILED or APP_SCHEDULER_RECOVERY_FAILED AppAttempt : LAUNCHED to FINAL_SAVING AppAttempt : FINAL_SAVING to FAILED App : FINAL_SAVING to FAILED Please give your suggestions/thoughts.
          Hide
          jianhe Jian He added a comment -

          Today, the semantics to stop a queue is to let the existing applications run into completion. We should retain the same semantics for RM restart as well. In this case, I think we need to ignore this exception and continue because the application was accepted before the queue is changed to stopped. Similar problem could happen if we change the application acl and restart RM while application is running.

          Show
          jianhe Jian He added a comment - Today, the semantics to stop a queue is to let the existing applications run into completion. We should retain the same semantics for RM restart as well. In this case, I think we need to ignore this exception and continue because the application was accepted before the queue is changed to stopped. Similar problem could happen if we change the application acl and restart RM while application is running.
          Hide
          rohithsharma Rohith Sharma K S added a comment -

          Thanks Jian He for your suggestion. I attached the patch fixing the issue for CapacityScheduler. I verified in deploying in real cluster also, it is working fine.
          Kindly review the patch.

          Show
          rohithsharma Rohith Sharma K S added a comment - Thanks Jian He for your suggestion. I attached the patch fixing the issue for CapacityScheduler. I verified in deploying in real cluster also, it is working fine. Kindly review the patch.
          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12687993/0001-YARN-2340.patch
          against trunk revision 1050d42.

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

          +1 tests included. The patch appears to include 1 new or modified test files.

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

          +1 javadoc. There were no new javadoc warning messages.

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

          -1 findbugs. The patch appears to introduce 14 new Findbugs (version 2.0.3) warnings.

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

          -1 core tests. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

          org.apache.hadoop.yarn.server.resourcemanager.TestRM

          Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6144//testReport/
          Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/6144//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
          Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6144//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12687993/0001-YARN-2340.patch against trunk revision 1050d42. +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. -1 findbugs . The patch appears to introduce 14 new Findbugs (version 2.0.3) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. -1 core tests . The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: org.apache.hadoop.yarn.server.resourcemanager.TestRM Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6144//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/6144//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6144//console This message is automatically generated.
          Hide
          rohithsharma Rohith Sharma K S added a comment -

          It looks failed tests is random. In my env, it is running successfully.

          Show
          rohithsharma Rohith Sharma K S added a comment - It looks failed tests is random. In my env, it is running successfully.
          Hide
          rohithsharma Rohith Sharma K S added a comment -

          Jian He Kindly review the patch

          Show
          rohithsharma Rohith Sharma K S added a comment - Jian He Kindly review the patch
          Hide
          jianhe Jian He added a comment -

          looks good, +1

          Show
          jianhe Jian He added a comment - looks good, +1
          Hide
          hadoopqa Hadoop QA added a comment -

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

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

          +1 tests included. The patch appears to include 1 new or modified test files.

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

          +1 javadoc. There were no new javadoc warning messages.

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

          -1 findbugs. The patch appears to introduce 15 new Findbugs (version 2.0.3) warnings.

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

          -1 core tests. The following test timeouts occurred in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

          org.apache.hadoop.yarn.server.resourcemanager.ahs.TestRMApplicationHistoryWriter

          Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6173//testReport/
          Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/6173//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
          Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6173//console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12687993/0001-YARN-2340.patch against trunk revision fdf042d. +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. -1 findbugs . The patch appears to introduce 15 new Findbugs (version 2.0.3) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. -1 core tests . The following test timeouts occurred in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: org.apache.hadoop.yarn.server.resourcemanager.ahs.TestRMApplicationHistoryWriter Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6173//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/6173//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6173//console This message is automatically generated.
          Hide
          rohithsharma Rohith Sharma K S added a comment -

          There so many tests are failing randomly in trunk!!

          Show
          rohithsharma Rohith Sharma K S added a comment - There so many tests are failing randomly in trunk!!
          Hide
          jianhe Jian He added a comment -

          right, we should spend time fixing these..

          Show
          jianhe Jian He added a comment - right, we should spend time fixing these..
          Hide
          jianhe Jian He added a comment -

          committed to trunk and branch-2, thanks Rohith !

          Show
          jianhe Jian He added a comment - committed to trunk and branch-2, thanks Rohith !
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-trunk-Commit #6777 (See https://builds.apache.org/job/Hadoop-trunk-Commit/6777/)
          YARN-2340. Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782)

          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java
          • hadoop-yarn-project/CHANGES.txt
          • 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
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-trunk-Commit #6777 (See https://builds.apache.org/job/Hadoop-trunk-Commit/6777/ ) YARN-2340 . Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java hadoop-yarn-project/CHANGES.txt 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
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #50 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/50/)
          YARN-2340. Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782)

          • hadoop-yarn-project/CHANGES.txt
          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java
          • 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
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #50 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/50/ ) YARN-2340 . Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782) hadoop-yarn-project/CHANGES.txt hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java 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
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Hadoop-Yarn-trunk #784 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/784/)
          YARN-2340. Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782)

          • hadoop-yarn-project/CHANGES.txt
          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java
          • 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
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-Yarn-trunk #784 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/784/ ) YARN-2340 . Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782) hadoop-yarn-project/CHANGES.txt hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java 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
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #47 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/47/)
          YARN-2340. Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782)

          • 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-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java
          • hadoop-yarn-project/CHANGES.txt
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #47 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/47/ ) YARN-2340 . Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782) 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-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java hadoop-yarn-project/CHANGES.txt
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Hadoop-Hdfs-trunk #1982 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1982/)
          YARN-2340. Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782)

          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java
          • 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-yarn-project/CHANGES.txt
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-Hdfs-trunk #1982 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1982/ ) YARN-2340 . Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java 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-yarn-project/CHANGES.txt
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #51 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/51/)
          YARN-2340. Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782)

          • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java
          • hadoop-yarn-project/CHANGES.txt
          • 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
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #51 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/51/ ) YARN-2340 . Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java hadoop-yarn-project/CHANGES.txt 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
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2001 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2001/)
          YARN-2340. Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782)

          • 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-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java
          • hadoop-yarn-project/CHANGES.txt
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2001 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2001/ ) YARN-2340 . Fixed NPE when queue is stopped during RM restart. Contributed by Rohith Sharmaks (jianhe: rev 0d89859b51157078cc504ac81dc8aa75ce6b1782) 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-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java hadoop-yarn-project/CHANGES.txt
          Hide
          vinodkv Vinod Kumar Vavilapalli added a comment -

          Pulled this into 2.6.1. Ran compilation and TestWorkPreservingRMRestart before the push. Patch applied cleanly.

          Show
          vinodkv Vinod Kumar Vavilapalli added a comment - Pulled this into 2.6.1. Ran compilation and TestWorkPreservingRMRestart before the push. Patch applied cleanly.

            People

            • Assignee:
              rohithsharma Rohith Sharma K S
              Reporter:
              nishan Nishan Shetty
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development