Oozie Failing To Start On MapR 4.1 With "org.apache.oozie.service.ServiceException: E0100: Could not initialize service [org.apache.oozie.service.HadoopAccessorService]"

Document created by mufeed on Feb 13, 2016
Version 1Show Document
  • View in full screen mode

Author: Mufeed Usman

 

Original Publication Date: April 14, 2015

 

Environment:

MapR Core 4.1.0

MapR Oozie 4.1.0

 

Symptom:

Oozie fails to start with the following stack,

 

2015-04-08 21:55:02,623 FATAL Services:535 - SERVER[n72] USER[-] GROUP[-]

E0100: Could not initialize service

[org.apache.oozie.service.HadoopAccessorService], null

org.apache.oozie.service.ServiceException: E0100: Could not initialize service

[org.apache.oozie.service.HadoopAccessorService], null

  at

org.apache.oozie.service.HadoopAccessorService.kerberosInit(HadoopAccessorService.java:196)

  at

org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:141)

  at

org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:112)

  at

org.apache.oozie.service.Services.setServiceInternal(Services.java:383)

  at org.apache.oozie.service.Services.setService(Services.java:369)

  at org.apache.oozie.service.Services.loadServices(Services.java:302)

  at org.apache.oozie.service.Services.init(Services.java:210)

  at

org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:45)

  at

org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4210)

  at

org.apache.catalina.core.StandardContext.start(StandardContext.java:4709)

  at

org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)

  at

org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)

  at

org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583)

  at

org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)

  at

org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)

  at

org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)

  at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)

  at

org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)

  at

org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)

  at

org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)

  at org.apache.catalina.core.StandardHost.start(StandardHost.java:822)

  at

org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)

  at

org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)

  at

org.apache.catalina.core.StandardService.start(StandardService.java:525)

  at

org.apache.catalina.core.StandardServer.start(StandardServer.java:754)

  at org.apache.catalina.startup.Catalina.start(Catalina.java:595)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

  at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

  at java.lang.reflect.Method.invoke(Method.java:606)

  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)

  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Root cause:

This happens when the oozie.war file in the Oozie install is built with an incorrect 'maprfs-.1.0mapr.jar' file when the cluster is in YARN mode.

 

Solution:

Request for patch mapr-patch-4.1.0.31175.GA-31295.x86_64.rpm from Support and apply it on the cluster to resolve the issue.

1 person found this helpful

Attachments

    Outcomes