HPE Ezmeral Software platform
1753504 Members
4964 Online
108794 Solutions
New Discussion

Re: Oozie not starting

 
SOLVED
Go to solution
MaksREDS
Occasional Advisor

Oozie not starting

I have an clean install of HPE EDF on 3-node cluster and Oozie service cannot start.

The DF was installed using default settings (secure cluster). All the other services have started succesfully.

It seems that required threads number is not provided (?). I've tried to change oozie.server.threadpool.max.threads variable (default: 150), but with no results.
The cluster runs on Ubuntu 18.04 - does it matter?

oozie-error.log :

2021-06-08 15:21:29,059  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:21:29,069  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:21:29,072  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:21:29,080  WARN DateUtils:523 - SERVER[] GMT, UTC or Region/City Timezone formats are preferred instead of UTC
2021-06-08 15:21:34,404  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:21:34,415  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:21:34,428  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:21:37,493  WARN ConfigurationService:523 - SERVER[our.node.name] System property [oozie.instance.id] no defined in Oozie configuration, ignored
2021-06-08 15:21:37,502  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:21:37,510  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:21:37,516  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.instance.id] 
2021-06-08 15:21:37,520  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:21:37,530  WARN DateUtils:523 - SERVER[our.node.name] GMT, UTC or Region/City Timezone formats are preferred instead of UTC
2021-06-08 15:21:38,059  WARN AuthorizationService:523 - SERVER[our.node.name] Oozie running with authorization disabled
2021-06-08 15:21:42,557  WARN SparkConfigurationService:523 - SERVER[our.node.name] Deprecated property found in configuration: oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jarUse oozie.service.SparkConfigurationService.spark.configurations.blacklist instead.
2021-06-08 15:21:42,558  WARN SparkConfigurationService:523 - SERVER[our.node.name] Spark Configuration could not be loaded for *: /opt/mapr/oozie/oozie-5.2.1/conf/spark-conf does not exist
2021-06-08 15:21:44,280 ERROR EmbeddedOozieServer:325 - SERVER[our.node.name] Could not start EmbeddedOozieServer! Error message: Insufficient configured threads: required=5 < max=5 for QueuedThreadPool[qtp1974062116]@75a9cc24{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@49e62b17{s=0/1,p=0}]
2021-06-08 15:22:06,672  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:22:06,673  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:22:06,674  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:22:06,677  WARN DateUtils:523 - SERVER[] GMT, UTC or Region/City Timezone formats are preferred instead of UTC
2021-06-08 15:22:10,651  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:22:10,651  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:22:10,651  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:22:12,323  WARN ConfigurationService:523 - SERVER[our.node.name] System property [oozie.instance.id] no defined in Oozie configuration, ignored
2021-06-08 15:22:12,327  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:22:12,327  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:22:12,328  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.instance.id] 
2021-06-08 15:22:12,329  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:22:12,332  WARN DateUtils:523 - SERVER[our.node.name] GMT, UTC or Region/City Timezone formats are preferred instead of UTC
2021-06-08 15:22:12,677  WARN AuthorizationService:523 - SERVER[our.node.name] Oozie running with authorization disabled
2021-06-08 15:22:15,919  WARN SparkConfigurationService:523 - SERVER[our.node.name] Deprecated property found in configuration: oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jarUse oozie.service.SparkConfigurationService.spark.configurations.blacklist instead.
2021-06-08 15:22:15,920  WARN SparkConfigurationService:523 - SERVER[our.node.name] Spark Configuration could not be loaded for *: /opt/mapr/oozie/oozie-5.2.1/conf/spark-conf does not exist
2021-06-08 15:22:17,299 ERROR EmbeddedOozieServer:325 - SERVER[our.node.name] Could not start EmbeddedOozieServer! Error message: Insufficient configured threads: required=5 < max=5 for QueuedThreadPool[qtp802435370]@2fd4312a{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@25464154{s=0/1,p=0}]
2021-06-08 15:22:48,258  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:22:48,259  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:22:48,260  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:22:48,264  WARN DateUtils:523 - SERVER[] GMT, UTC or Region/City Timezone formats are preferred instead of UTC
2021-06-08 15:22:52,224  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:22:52,225  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:22:52,225  WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:22:53,991  WARN ConfigurationService:523 - SERVER[our.node.name] System property [oozie.instance.id] no defined in Oozie configuration, ignored
2021-06-08 15:22:53,995  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.hosts] 
2021-06-08 15:22:53,996  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.mapr.groups] 
2021-06-08 15:22:53,996  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [oozie.instance.id] 
2021-06-08 15:22:53,997  WARN ConfigurationService:523 - SERVER[our.node.name] Invalid configuration defined, [hadoop.security.credential.provider.path] 
2021-06-08 15:22:54,001  WARN DateUtils:523 - SERVER[our.node.name] GMT, UTC or Region/City Timezone formats are preferred instead of UTC
2021-06-08 15:22:54,333  WARN AuthorizationService:523 - SERVER[our.node.name] Oozie running with authorization disabled
2021-06-08 15:22:57,769  WARN SparkConfigurationService:523 - SERVER[our.node.name] Deprecated property found in configuration: oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jarUse oozie.service.SparkConfigurationService.spark.configurations.blacklist instead.
2021-06-08 15:22:57,769  WARN SparkConfigurationService:523 - SERVER[our.node.name] Spark Configuration could not be loaded for *: /opt/mapr/oozie/oozie-5.2.1/conf/spark-conf does not exist
2021-06-08 15:22:59,150 ERROR EmbeddedOozieServer:325 - SERVER[our.node.name] Could not start EmbeddedOozieServer! Error message: Insufficient configured threads: required=5 < max=5 for QueuedThreadPool[qtp1975727624]@75c33608{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@4449a60b{s=0/1,p=0}]

 

jetty.log:

2021-06-08 15:22:50,916  INFO log:169 - Logging initialized @3736ms to org.eclipse.jetty.util.log.Slf4jLog
2021-06-08 15:22:57,974  INFO log:169 - Logging initialized @5368ms to org.eclipse.jetty.util.log.Slf4jLog
2021-06-08 15:22:58,288  INFO Server:375 - jetty-9.4.39.v20210325; built: 2021-03-25T14:42:11.471Z; git: 9fc7ca5a922f2a37b84ec9dbc26a5168cee7e667; jvm 11.0.3+7
2021-06-08 15:22:58,589  WARN StandardDescriptorProcessor:1213 - Duplicate mapping from / to default
2021-06-08 15:22:58,590  WARN StandardDescriptorProcessor:1213 - Duplicate mapping from *.jsp to jsp
2021-06-08 15:22:59,003  INFO session:334 - DefaultSessionIdManager workerName=node0
2021-06-08 15:22:59,003  INFO session:339 - No SessionScavenger set, using defaults
2021-06-08 15:22:59,005  INFO session:132 - node0 Scavenging every 660000ms
2021-06-08 15:22:59,084  INFO ContextHandler:916 - Started o.e.j.w.WebAppContext@5d66ae3a{/oozie,file:///opt/mapr/oozie/oozie-5.2.1/embedded-oozie-server/webapp/,AVAILABLE}{file:///opt/mapr/oozie/oozie-5.2.1/embedded-oozie-server/webapp/}
2021-06-08 15:22:59,110  INFO AbstractConnector:331 - Started ServerConnector@240a2619{HTTP/1.1, (http/1.1)}{0.0.0.0:11000}
2021-06-08 15:22:59,119  INFO SslContextFactory:357 - x509=X509@35becbd4(dev.reds.com.pl,h=[],w=[dev.reds.com.pl]) for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,128  WARN config:289 - Weak cipher suite TLS_RSA_WITH_AES_256_GCM_SHA384 enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,128  WARN config:289 - Weak cipher suite TLS_RSA_WITH_AES_128_GCM_SHA256 enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,129  WARN config:289 - Weak cipher suite TLS_RSA_WITH_AES_256_CBC_SHA256 enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,129  WARN config:289 - Weak cipher suite TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,129  WARN config:289 - Weak cipher suite TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,130  WARN config:289 - Weak cipher suite TLS_RSA_WITH_AES_256_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,130  WARN config:289 - Weak cipher suite TLS_RSA_WITH_AES_256_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,130  WARN config:289 - Weak cipher suite TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,130  WARN config:289 - Weak cipher suite TLS_ECDH_RSA_WITH_AES_256_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,130  WARN config:289 - Weak cipher suite TLS_DHE_RSA_WITH_AES_256_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,130  WARN config:289 - Weak cipher suite TLS_DHE_DSS_WITH_AES_256_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,130  WARN config:289 - Weak cipher suite TLS_RSA_WITH_AES_128_CBC_SHA256 enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,131  WARN config:289 - Weak cipher suite TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,131  WARN config:289 - Weak cipher suite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,131  WARN config:289 - Weak cipher suite TLS_RSA_WITH_AES_128_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,131  WARN config:289 - Weak cipher suite TLS_RSA_WITH_AES_128_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,131  WARN config:289 - Weak cipher suite TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,131  WARN config:289 - Weak cipher suite TLS_ECDH_RSA_WITH_AES_128_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,132  WARN config:289 - Weak cipher suite TLS_DHE_RSA_WITH_AES_128_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,132  WARN config:289 - Weak cipher suite TLS_DHE_DSS_WITH_AES_128_CBC_SHA enabled for Server@53bb71e5[provider=null,keyStore=file:///opt/mapr/conf/ssl_keystore,trustStore=null]
2021-06-08 15:22:59,139  INFO AbstractConnector:331 - Started ServerConnector@1a717d79{SSL, (ssl, http/1.1)}{0.0.0.0:11443}
2021-06-08 15:22:59,139  INFO Server:415 - Started @6533ms
2021-06-08 15:22:59,142  INFO Server:375 - jetty-9.4.39.v20210325; built: 2021-03-25T14:42:11.471Z; git: 9fc7ca5a922f2a37b84ec9dbc26a5168cee7e667; jvm 11.0.3+7
2021-06-08 15:22:59,145  INFO ContextHandler:916 - Started o.e.j.s.h.ContextHandler@73385d3f{/status,null,AVAILABLE}
2021-06-08 15:22:59,146  INFO ThreadPoolBudget:182 - ReservedThreadExecutor@4449a60b{s=0/1,p=0} requires 1 threads from QueuedThreadPool[qtp1975727624]@75c33608{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@4449a60b{s=0/1,p=0}]
2021-06-08 15:22:59,146  INFO ThreadPoolBudget:182 - ServerConnector@68d8ae27{HTTP/1.1, (http/1.1)}{localhost:21443} requires 4 threads from QueuedThreadPool[qtp1975727624]@75c33608{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@4449a60b{s=0/1,p=0}]
2021-06-08 15:22:59,147  WARN AbstractLifeCycle:235 - FAILED ServerConnector@68d8ae27{HTTP/1.1, (http/1.1)}{localhost:21443}: java.lang.IllegalStateException: Insufficient configured threads: required=5 < max=5 for QueuedThreadPool[qtp1975727624]@75c33608{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@4449a60b{s=0/1,p=0}]
java.lang.IllegalStateException: Insufficient configured threads: required=5 < max=5 for QueuedThreadPool[qtp1975727624]@75c33608{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@4449a60b{s=0/1,p=0}]
	at org.eclipse.jetty.util.thread.ThreadPoolBudget.check(ThreadPoolBudget.java:165)
	at org.eclipse.jetty.util.thread.ThreadPoolBudget.leaseTo(ThreadPoolBudget.java:141)
	at org.eclipse.jetty.util.thread.ThreadPoolBudget.leaseFrom(ThreadPoolBudget.java:191)
	at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:320)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.eclipse.jetty.server.Server.doStart(Server.java:401)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.apache.oozie.server.OozieStatusServer.start(OozieStatusServer.java:54)
	at org.apache.oozie.server.EmbeddedOozieServer.start(EmbeddedOozieServer.java:270)
	at org.apache.oozie.server.EmbeddedOozieServer.main(EmbeddedOozieServer.java:323)
2021-06-08 15:22:59,150  WARN AbstractLifeCycle:235 - FAILED Server@58ebee9{FAILED}[9.4.39.v20210325]: java.lang.IllegalStateException: Insufficient configured threads: required=5 < max=5 for QueuedThreadPool[qtp1975727624]@75c33608{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@4449a60b{s=0/1,p=0}]
java.lang.IllegalStateException: Insufficient configured threads: required=5 < max=5 for QueuedThreadPool[qtp1975727624]@75c33608{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@4449a60b{s=0/1,p=0}]
	at org.eclipse.jetty.util.thread.ThreadPoolBudget.check(ThreadPoolBudget.java:165)
	at org.eclipse.jetty.util.thread.ThreadPoolBudget.leaseTo(ThreadPoolBudget.java:141)
	at org.eclipse.jetty.util.thread.ThreadPoolBudget.leaseFrom(ThreadPoolBudget.java:191)
	at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:320)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.eclipse.jetty.server.Server.doStart(Server.java:401)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.apache.oozie.server.OozieStatusServer.start(OozieStatusServer.java:54)
	at org.apache.oozie.server.EmbeddedOozieServer.start(EmbeddedOozieServer.java:270)
	at org.apache.oozie.server.EmbeddedOozieServer.main(EmbeddedOozieServer.java:323)

 

10 REPLIES 10
tdunning
HPE Pro

Re: Oozie not starting

 

I know nothing about Oozie. BUT ...

Which version of data fabric did you install?

You say three nodes. How much memory and disk on each? How many cores?

I work for HPE
MaksREDS
Occasional Advisor

Re: Oozie not starting

Data Fabric 6.2.0

Each node:

  • 64 GB RAM
  • 2x8 core CPU (32 threads in total)
  • 3x240 GB HDD for MapRFS + 240GB for OS
Shishir_Prakash
HPE Pro

Re: Oozie not starting

What is the version of MapR Core and Oozie you are using? can you please provide "rpm -qa |grep mapr" from oozie node.  

The below error which you have reported is found in internal jira OOZ-252 . The fix for the same will be available in MEP-7.2.0

2021-06-08 15:22:17,299 ERROR EmbeddedOozieServer:325 - SERVER[our.node.name] Could not start EmbeddedOozieServer! Error message: Insufficient configured threads: required=5 < max=5 for QueuedThreadPool[qtp802435370]@2fd4312a{STARTED,5<=5<=5,i=5,r=-1,q=0}[ReservedThreadExecutor@25464154{s=0/1,p=0}]

 

I work for HPE. .
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
prakharr
Frequent Visitor

Re: Oozie not starting

1.Please check https://docs.datafabric.hpe.com/61/InteropMatrix/r_os_matrix_6.x.html

2. Can you elaborate what exactly you are doing in oozie ?

3. are you not able to start the oozie server or your job is failing?

4. what kind of job you are running ?

5. rpm -qa|grep mapr

6. are you able to run the same job directly on relaevnt ecosytem component ?

7. Is it a new setup ?

 

Harshkohli
HPE Pro

Re: Oozie not starting

I agree with the answers above and the stacktrace looks like OOZ-252. Fix for the same is available in MEP 7.2.0.

BTW, if you can provide the core and oozie version used, that might help to understand the background more.

I work for HPE
MaksREDS
Occasional Advisor

Re: Oozie not starting

 

1.Please check https://docs.datafabric.hpe.com/61/InteropMatrix/r_os_matrix_6.x.html

Ubuntu (18.04) and DF (6.2) versions are compatible

2. Can you elaborate what exactly you are doing in oozie ?

The Oozie service (this one that can be managed via MCS) has never started successfully, so I was not able to do anything.

3. are you not able to start the oozie server or your job is failing?

Not able to start the oozie server.

4. what kind of job you are running ?

No job running yet.

5. rpm -qa|grep mapr

$ dpkg -l | grep mapr
ii  mapr-asynchbase                        1.8.2.202104220851                              all          MapR: Asynchbase binary package. 
ii  mapr-client                            6.2.0.0.20200915234957.GA-1                     amd64        MapR: Client package
ii  mapr-collectd                          5.10.0.0.202104301721                           amd64        MapR: collectd package
ii  mapr-core                              6.2.0.0.20200915234957.GA-1                     amd64        MapR: core package
ii  mapr-core-internal                     6.2.0.0.20200915234957.GA-1                     amd64        MapR: Core Internal package
ii  mapr-drill                             1.16.1.200.202105180709                         all          Apache Drill Package, built for the MapR profile - Commit ID 
ii  mapr-drill-internal                    1.16.1.200.202105180709                         all          MapR: Drill Internal Package
ii  mapr-fileserver                        6.2.0.0.20200915234957.GA-1                     amd64        MapR: fileserver role package
ii  mapr-hadoop-client                     2.7.5.0.202105131403                            amd64        MapR: MapR hadoop client package
ii  mapr-hadoop-core                       2.7.5.0.202105131403                            amd64        MapR: MapR hadoop core package
ii  mapr-hadoop-util                       2.7.5.0.202105131403                            amd64        MapR: MapR hadoop util package
ii  mapr-hbase                             1.4.13.0.202105170751                           all          MapR: HBase binary package
ii  mapr-hbase-rest                        1.4.13.0.202105170751                           all          MapR: Hbase REST roles package.
ii  mapr-hbasethrift                       1.4.13.0.202105170751                           all          MapR: Hbase Thrift Server roles package.
ii  mapr-historyserver                     2.7.5.0.202105131403                            amd64        MapR: hadoop 2 history server package
ii  mapr-hive                              2.3.202105190211                                all          MapR: Hive package
ii  mapr-hivemetastore                     2.3.202105190211                                all          MapR: HiveMetastore roles package.
ii  mapr-hiveserver2                       2.3.202105190211                                all          MapR: HiveServer2 roles package.
ii  mapr-hivewebhcat                       2.3.202105190211                                all          MapR: HiveWebhcat roles package.
ii  mapr-httpfs                            1.1.0.0.202105130703                            all          MapR: HttpFS binary package.  
ii  mapr-hue                               4.6.0.0.202105070812                            all          MapR: Hue binary package.
ii  mapr-kafka                             2.1.1.200.202105140421                          all          MapR: Kafka package
ii  mapr-ksql                              5.1.2.200.202105140827                          all          MapR: KSQL roles package.
ii  mapr-ksql-internal                     5.1.2.200.202105140827                          all          MapR: KSQL internal package
ii  mapr-librdkafka                        0.11.3.202104281722                             amd64        MapR: librdkafka package
ii  mapr-loopbacknfs                       6.2.0.0.20200915234957.GA-1                     amd64        MapR: Loopback NFS package
ii  mapr-mastgateway                       6.2.0.0.20200915234957.GA-1                     amd64        MapR: mastgateway role package
ii  mapr-nodemanager                       2.7.5.0.202105131403                            amd64        MapR: hadoop 2 node manager package
ii  mapr-oozie                             5.2.1.0.202105180727                            all          MapR: Oozie roles package.
ii  mapr-oozie-internal                    5.2.1.0.202105180727                            all          MapR: Oozie Internal binary package.
ii  mapr-opentsdb                          2.4.0.202105181725                              all          MapR: opentsdb package
ii  mapr-spark                             2.4.7.100.202105170615                          all          MapR: Spark package
ii  mapr-spark-historyserver               2.4.7.100.202105170615                          all          MapR: Spark History Server package
ii  mapr-spark-thriftserver                2.4.7.100.202105170615                          all          MapR: Spark Thrift Server package
ii  mapr-zk-internal                       6.2.0.0.20200915234957.GA-1                     amd64        MapR: zookeeper binary package
ii  mapr-zookeeper                         6.2.0.0.20200915234957.GA-1                     amd64        MapR: zookeeper role package

 

6. are you able to run the same job directly on relaevnt ecosytem component ?

I would like to have working DF first, than I will start some jobs.

7. Is it a new setup ?

Yes - clean install of DF, clean install of Ubuntu (bare metal).

 

Harshkohli
HPE Pro

Re: Oozie not starting

Thanks for the details. I can check that the oozie updated code base for 7.2 has the max threads parameter included there so you should be fine with MEP 7.2.0.

MEP 7.2.0 will be out soon and it would be great to wait for sometime since you are already using MEP 7.1.0.

I work for HPE
Harshkohli
HPE Pro

Re: Oozie not starting

Kindly let us know if the suggested solution below works Ok for you and can be marked as a response. As mentioned it should be taken care in MEP 7.2

I work for HPE
Harshkohli
HPE Pro
Solution

Re: Oozie not starting

Team,

As we are discusisng over the case. This fix has been backported and is now available for below rpm's. The patch has been uploaded over sftp. Kindly use the latest rpm for MEP 7.1.0 under oozie directory.
Below are the patches.
mapr-oozie-5.2.1.1.202109092302-1.noarch.rpm
mapr-oozie-internal-5.2.1.1.202109092302-1.noarch.rpm

Kindly let me know if its works and feel free to accept it as a solution.

 

Regards.

I work for HPE