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

On branch-2 ResourceManager failed to start

    Details

    • Type: Bug
    • Status: Open
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: 2.9.0
    • Fix Version/s: None
    • Component/s: resourcemanager
    • Labels:
      None

      Description

      On build against branch-2, ResourceManager get failed to start because of following failures:

      2017-07-16 23:33:15,688 FATAL org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting ResourceManager
      java.lang.NoSuchMethodError: org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.ContainerAllocationExpirer.setMonitorInterval(I)V
              at org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.ContainerAllocationExpirer.serviceInit(ContainerAllocationExpirer.java:44)
              at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
              at org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
              at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$RMActiveServices.serviceInit(ResourceManager.java:684)
              at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
              at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.createAndInitActiveServices(ResourceManager.java:1005)
              at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.serviceInit(ResourceManager.java:285)
              at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
              at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.main(ResourceManager.java:1283)
      

        Activity

        Hide
        jlowe Jason Lowe added a comment -

        I'm not able to reproduce this. Usually a NSM error like this implies the jars that were provided at runtime do not match the ones used at compile time. Possibly something came along after the compile that corrupted your build?

        Show
        jlowe Jason Lowe added a comment - I'm not able to reproduce this. Usually a NSM error like this implies the jars that were provided at runtime do not match the ones used at compile time. Possibly something came along after the compile that corrupted your build?

          People

          • Assignee:
            Unassigned
            Reporter:
            djp Junping Du
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Development