Issue with Oozie after upgrading Ambari

[#1]

After upgrading Ambari from 2.2.1.1 to 2.2.2.0, I get the following error when attempting to start Oozie. My HDP version is HDP-2.4.0.0-169. Any thoughts or workarounds?

2016-05-11 21:53:45,763 FATAL Services - SERVER[deadpool.lab.local] E0113: class not found [org.apache.oozie.extensions.OozieELExtensions]
org.apache.oozie.service.ServiceException: E0113: class not found [org.apache.oozie.extensions.OozieELExtensions]
	at org.apache.oozie.service.ELService.findMethod(ELService.java:226)
	at org.apache.oozie.service.ELService.extractFunctions(ELService.java:104)
	at org.apache.oozie.service.ELService.init(ELService.java:135)
	at org.apache.oozie.service.Services.setServiceInternal(Services.java:386)
	at org.apache.oozie.service.Services.setService(Services.java:372)
	at org.apache.oozie.service.Services.loadServices(Services.java:305)
	at org.apache.oozie.service.Services.init(Services.java:213)
	at org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
	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:802)
	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:676)
	at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:602)
	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:503)
	at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322)
	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1068)
	at org.apache.catalina.core.StandardHost.start(StandardHost.java:822)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1060)
	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:759)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) 
2016-05-11 21:53:45,768 INFO Services - SERVER[deadpool.lab.local] Shutdown 

[#2 · Accepted solution]

@Tim Veil

1. Can you please copy falcon-<version>.jar to /usr/hdp/current/oozie-server/libext/

2. Stop Oozie server daemon

3. Run Oozie prepare war command

/usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war 

4. Start oozie server

[#3]

I copied falcon.jar from /usr/hdp/current/falcon-server/client/lib and ran prepare-war. That did the trick. Many thanks!

[#4]

To be more exact copy the falcon-oozie-el-extension where you can find it in /usr/hdp/current/falcon/oozie/ext/falcon-oozie-el-ext" to /usr/hdp/current/oozie-server/libext/ Run Oozie prepare war command and start the oozie server. It sghould work 🙂

[#5]

It seems like falcon<version>jar is missing, can you check it in /usr/hdp/current/oozie-server/libext directory? if its not therethen kindly copy it and rebuild the oozie war.

[#6]

Note the falcon jar actually needed is:

/usr/hdp/current/falcon-server/oozie/ext/falcon-oozie-el-extension.jar

NOT the cli or client falcon jar files.

[#7]

All,

This is actually a BUG, as ambari removes the falcon service but not the hooks in Oozie configs. The proper way to fix this and not have it hit you each time you upgrade is to remove the below listed values from your oozie configs. I have also opened an internal (to Hortonworks) JIRA to have this fixed in future versions of Ambari.

oozie.service.ProxyUserService.proxyuser.falcon.hosts
oozie.service.ProxyUserService.proxyuser.falcon.groups
oozie.service.URIHandlerService.uri.handlers
oozie.services.ext
oozie.service.ELService.ext.functions.coord-job-submit-instances
oozie.service.ELService.ext.functions.coord-action-create-inst
oozie.service.ELService.ext.functions.coord-action-create
oozie.service.ELService.ext.functions.coord-job-submit-data
oozie.service.ELService.ext.functions.coord-action-start
oozie.service.ELService.ext.functions.coord-sla-submit
oozie.service.ELService.ext.functions.coord-sla-create

[#8]

I had to remove following properties as well,

oozie.service.ELService.ext.functions.workflow

oozie.service.ELService.ext.functions.coord-sla-create

On the whole, had to make sure there are no oozie.extensions and ELService Functions that were used in the oozie-site.xml.

Thank you @Kuldeep Kulkarni and @Orlando Teixeira