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

Missing NullPointer check in AppSchedulingInfo causes RM to die

    Details

    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      In AppSchedulingInfo.java the method checkForDeactivation() has these 2 consecutive lines:

      ResourceRequest request = getResourceRequest(priority, ResourceRequest.ANY);
      if (request.getNumContainers() > 0) {
      

      the first line calls getResourceRequest and it can return null.

      synchronized public ResourceRequest getResourceRequest(
      Priority priority, String resourceName) {
          Map<String, ResourceRequest> nodeRequests = requests.get(priority);
          return  (nodeRequests == null) ? {color:red} null : nodeRequests.get(resourceName);
      }
      

      The second line dereferences the pointer directly without a check.
      If the pointer is null, the RM dies.

      2015-03-17 14:14:04,757 FATAL org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in handling event type NODE_UPDATE to the scheduler
      java.lang.NullPointerException
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.AppSchedulingInfo.checkForDeactivation(AppSchedulingInfo.java:383)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.AppSchedulingInfo.decrementOutstanding(AppSchedulingInfo.java:375)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.AppSchedulingInfo.allocateOffSwitch(AppSchedulingInfo.java:360)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.AppSchedulingInfo.allocate(AppSchedulingInfo.java:270)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.common.fica.FiCaSchedulerApp.allocate(FiCaSchedulerApp.java:142)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.assignContainer(LeafQueue.java:1559)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.assignOffSwitchContainers(LeafQueue.java:1384)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.assignContainersOnNode(LeafQueue.java:1263)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.assignContainers(LeafQueue.java:816)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue.assignContainersToChildQueues(ParentQueue.java:588)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue.assignContainers(ParentQueue.java:449)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.allocateContainersToNode(CapacityScheduler.java:1017)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:1059)
      at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:114)
      at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:739)
      at java.lang.Thread.run(Thread.java:722)
      2015-03-17 14:14:04,758 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Exiting, bbye..

      1. YARN-3369.2.patch
        1 kB
        Wangda Tan
      2. YARN-3369.patch
        1 kB
        Brahma Reddy Battula
      3. YARN-3369-003.patch
        2 kB
        Brahma Reddy Battula

        Activity

        Hide
        brahmareddy Brahma Reddy Battula added a comment -

        Giovanni Matteo Fumarola thanks for reporting..I would like to work on this jira, If you have patch, you can reassign to yourself...thanks

        Show
        brahmareddy Brahma Reddy Battula added a comment - Giovanni Matteo Fumarola thanks for reporting..I would like to work on this jira, If you have patch, you can reassign to yourself...thanks
        Hide
        kasha Karthik Kambatla added a comment -

        It would be good to avoid the NPE, however I am surprised we run into this. If there are no ANY requests, why are we allocating a container? Is this an indicator of a scheduler bug?

        Show
        kasha Karthik Kambatla added a comment - It would be good to avoid the NPE, however I am surprised we run into this. If there are no ANY requests, why are we allocating a container? Is this an indicator of a scheduler bug?
        Hide
        giovanni.fumarola Giovanni Matteo Fumarola added a comment -

        You can work on it.

        Show
        giovanni.fumarola Giovanni Matteo Fumarola added a comment - You can work on it.
        Hide
        leftnoteasy Wangda Tan added a comment -

        Took a look at code, this happens when:
        1) Application request a resource request (name != *) under a priority, there's no off switch resource request under the priority.
        2) Allocate any container under any other priority will trigger the issue.

        I think add a null check in checkForDeactivation should be sufficient.

        Show
        leftnoteasy Wangda Tan added a comment - Took a look at code, this happens when: 1) Application request a resource request (name != *) under a priority, there's no off switch resource request under the priority. 2) Allocate any container under any other priority will trigger the issue. I think add a null check in checkForDeactivation should be sufficient.
        Hide
        leftnoteasy Wangda Tan added a comment -

        Increased priority to blocker since this will cause RM down no matter which scheduler we are using.

        Show
        leftnoteasy Wangda Tan added a comment - Increased priority to blocker since this will cause RM down no matter which scheduler we are using.
        Hide
        leftnoteasy Wangda Tan added a comment -

        As far as I can see, this should only happen when user writes their own application, using ApplicationMasterProtocol (instead of AMRMClient). AMRMClient will handle the case – when user require a host or rack under a priority, offswitch resource request will be added automatically.

        Show
        leftnoteasy Wangda Tan added a comment - As far as I can see, this should only happen when user writes their own application, using ApplicationMasterProtocol (instead of AMRMClient). AMRMClient will handle the case – when user require a host or rack under a priority, offswitch resource request will be added automatically.
        Hide
        brahmareddy Brahma Reddy Battula added a comment -

        Yes,Adding null check is sufficient..priority can null if container got allocated under any other priority,,please check the following snippet for same..

        Map<String, ResourceRequest> nodeRequests = requests.get(priority);
            return (nodeRequests == null) ? null : nodeRequests.get(resourceName);
        
        Show
        brahmareddy Brahma Reddy Battula added a comment - Yes,Adding null check is sufficient..priority can null if container got allocated under any other priority,,please check the following snippet for same.. Map< String , ResourceRequest> nodeRequests = requests.get(priority); return (nodeRequests == null ) ? null : nodeRequests.get(resourceName);
        Hide
        brahmareddy Brahma Reddy Battula added a comment -

        Attached patch ..Wangda Tan and Karthik Kambatla kindly review!!

        Show
        brahmareddy Brahma Reddy Battula added a comment - Attached patch .. Wangda Tan and Karthik Kambatla kindly review!!
        Hide
        leftnoteasy Wangda Tan added a comment -

        Mostly LGTM, could you make code inner {{if ... }} indent?

        Show
        leftnoteasy Wangda Tan added a comment - Mostly LGTM, could you make code inner {{if ... }} indent?
        Hide
        leftnoteasy Wangda Tan added a comment -

        I think we don't need check null here, since Map<String, RR> will be always created when priority added.

        Show
        leftnoteasy Wangda Tan added a comment - I think we don't need check null here, since Map<String, RR> will be always created when priority added.
        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/12705656/YARN-3369.patch
        against trunk revision 61a4c7f.

        +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 generated 1152 javac compiler warnings (more than the trunk's current 206 warnings).

        -1 javadoc. The javadoc tool appears to have generated 43 warning messages.
        See https://builds.apache.org/job/PreCommit-YARN-Build/7026//artifact/patchprocess/diffJavadocWarnings.txt for details.

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

        +1 findbugs. The patch does not introduce any 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-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs:

        org.apache.hadoop.ipc.TestRPCWaitForProxy
        org.apache.hadoop.tracing.TestTracing
        org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
        org.apache.hadoop.hdfs.qjournal.TestSecureNNWithQJM

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7026//testReport/
        Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/7026//artifact/patchprocess/diffJavacWarnings.txt
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7026//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/12705656/YARN-3369.patch against trunk revision 61a4c7f. +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 generated 1152 javac compiler warnings (more than the trunk's current 206 warnings). -1 javadoc . The javadoc tool appears to have generated 43 warning messages. See https://builds.apache.org/job/PreCommit-YARN-Build/7026//artifact/patchprocess/diffJavadocWarnings.txt for details. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any 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-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.ipc.TestRPCWaitForProxy org.apache.hadoop.tracing.TestTracing org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover org.apache.hadoop.hdfs.qjournal.TestSecureNNWithQJM Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7026//testReport/ Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/7026//artifact/patchprocess/diffJavacWarnings.txt Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7026//console This message is automatically generated.
        Hide
        leftnoteasy Wangda Tan added a comment -

        Attached same patch with correct indent, will commit when Jenkins get back.

        Show
        leftnoteasy Wangda Tan added a comment - Attached same patch with correct indent, will commit when Jenkins get back.
        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/12705751/YARN-3369.2.patch
        against trunk revision 91baca1.

        +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. There were no new javadoc warning messages.

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

        +1 findbugs. The patch does not introduce any 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 passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7032//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7032//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/12705751/YARN-3369.2.patch against trunk revision 91baca1. +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 . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any 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 passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7032//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7032//console This message is automatically generated.
        Hide
        brahmareddy Brahma Reddy Battula added a comment -

        Thanks a lot!!!

        Show
        brahmareddy Brahma Reddy Battula added a comment - Thanks a lot!!!
        Hide
        rohithsharma Rohith Sharma K S added a comment -

        Thanks Brahma Reddy Battula for providing patch.
        I think all the caller of getResourceRequest() needs be verified for null check. Below code also should check for null else NPE can be thrown.

         public synchronized Resource getResource(Priority priority) {
            ResourceRequest request = getResourceRequest(priority, ResourceRequest.ANY);
            return request.getCapability();
          }
        
        Show
        rohithsharma Rohith Sharma K S added a comment - Thanks Brahma Reddy Battula for providing patch. I think all the caller of getResourceRequest() needs be verified for null check. Below code also should check for null else NPE can be thrown. public synchronized Resource getResource(Priority priority) { ResourceRequest request = getResourceRequest(priority, ResourceRequest.ANY); return request.getCapability(); }
        Hide
        brahmareddy Brahma Reddy Battula added a comment -

        Thanks for taking look into this issue..Yes.I missed this one..Updated the patch

        Show
        brahmareddy Brahma Reddy Battula added a comment - Thanks for taking look into this issue..Yes.I missed this one..Updated the patch
        Hide
        leftnoteasy Wangda Tan added a comment -

        Thanks for Rohith Sharma K S for the additional review, getResource is only used by tests, but it's better to add null check.

        Latest patch LGTM, will commit once Jenkins get back.

        Show
        leftnoteasy Wangda Tan added a comment - Thanks for Rohith Sharma K S for the additional review, getResource is only used by tests, but it's better to add null check. Latest patch LGTM, will commit once Jenkins get back.
        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/12705912/YARN-3369-003.patch
        against trunk revision 8041267.

        +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. There were no new javadoc warning messages.

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

        +1 findbugs. The patch does not introduce any 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.TestRM

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7040//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7040//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/12705912/YARN-3369-003.patch against trunk revision 8041267. +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 . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any 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.TestRM Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7040//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7040//console This message is automatically generated.
        Hide
        leftnoteasy Wangda Tan added a comment -

        Committed to trunk/branch-2/branch-2.7, verified failed test is not related.

        Thanks for Giovanni Matteo Fumarola reporting, Brahma Reddy Battula working on the patch and review from Rohith Sharma K S and Karthik Kambatla!

        Show
        leftnoteasy Wangda Tan added a comment - Committed to trunk/branch-2/branch-2.7, verified failed test is not related. Thanks for Giovanni Matteo Fumarola reporting, Brahma Reddy Battula working on the patch and review from Rohith Sharma K S and Karthik Kambatla !
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-trunk-Commit #7384 (See https://builds.apache.org/job/Hadoop-trunk-Commit/7384/)
        YARN-3369. Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72)

        • 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/AppSchedulingInfo.java
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-trunk-Commit #7384 (See https://builds.apache.org/job/Hadoop-trunk-Commit/7384/ ) YARN-3369 . Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72) 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/AppSchedulingInfo.java
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #139 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/139/)
        YARN-3369. Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72)

        • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AppSchedulingInfo.java
        • hadoop-yarn-project/CHANGES.txt
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #139 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/139/ ) YARN-3369 . Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AppSchedulingInfo.java hadoop-yarn-project/CHANGES.txt
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Yarn-trunk #873 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/873/)
        YARN-3369. Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72)

        • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AppSchedulingInfo.java
        • hadoop-yarn-project/CHANGES.txt
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Yarn-trunk #873 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/873/ ) YARN-3369 . Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AppSchedulingInfo.java hadoop-yarn-project/CHANGES.txt
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Mapreduce-trunk #2089 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2089/)
        YARN-3369. Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72)

        • 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/AppSchedulingInfo.java
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk #2089 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2089/ ) YARN-3369 . Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72) 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/AppSchedulingInfo.java
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Hdfs-trunk #2071 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2071/)
        YARN-3369. Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72)

        • 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/AppSchedulingInfo.java
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk #2071 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2071/ ) YARN-3369 . Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72) 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/AppSchedulingInfo.java
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #130 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/130/)
        YARN-3369. Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72)

        • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AppSchedulingInfo.java
        • hadoop-yarn-project/CHANGES.txt
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #130 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/130/ ) YARN-3369 . Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AppSchedulingInfo.java hadoop-yarn-project/CHANGES.txt
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #139 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/139/)
        YARN-3369. Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72)

        • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AppSchedulingInfo.java
        • hadoop-yarn-project/CHANGES.txt
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #139 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/139/ ) YARN-3369 . Missing NullPointer check in AppSchedulingInfo causes RM to die. (Brahma Reddy Battula via wangda) (wangda: rev 6bc7710ec7f2592c4c87dd940fbe5827ef81fe72) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AppSchedulingInfo.java hadoop-yarn-project/CHANGES.txt
        Hide
        sjlee0 Sangjin Lee added a comment -

        The patch applies to 2.6.0 cleanly.

        Show
        sjlee0 Sangjin Lee added a comment - The patch applies to 2.6.0 cleanly.
        Hide
        vinodkv Vinod Kumar Vavilapalli added a comment -

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

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

          People

          • Assignee:
            brahmareddy Brahma Reddy Battula
            Reporter:
            giovanni.fumarola Giovanni Matteo Fumarola
          • Votes:
            0 Vote for this issue
            Watchers:
            17 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development