Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

problem in beeline query execution

problem in beeline query execution

New Contributor

Hi,

I am facing issue to run the query on Hbase link hive table for insert from beeline as well as from oozie hive2 action.

Exit code: 255

Stack trace: ExitCodeException exitCode=255:

at org.apache.hadoop.util.Shell.runCommand(Shell.java:576)

at org.apache.hadoop.util.Shell.run(Shell.java:487)

at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:753)

at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:211)

at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:302)

at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:82)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Container exited with a non-zero exit code 255

Failing this attempt. Failing the application.

at org.apache.tez.client.TezClient.waitTillReady(TezClient.java:718)

at org.apache.hadoop.hive.ql.exec.tez.TezSessionState.open(TezSessionState.java:207)

at org.apache.hadoop.hive.ql.exec.tez.TezTask.updateSession(TezTask.java:257)

at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:140)

at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)

at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)

at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1655)

at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1414)

at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1195)

at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1059)

at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1054)

at org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:154)

at org.apache.hive.service.cli.operation.SQLOperation.access$100(SQLOperation.java:71)

at org.apache.hive.service.cli.operation.SQLOperation$1$1.run(SQLOperation.java:206)

at java.security.AccessController.doPrivileged(Native Method)

at javax.security.auth.Subject.doAs(Subject.java:422)

at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)

at org.apache.hive.service.cli.operation.SQLOperation$1.run(SQLOperation.java:218)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Error: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask (state=08S01,code=1)

The same error I am getting when I am trying to run the query via oozie hive2 action and in the detail yarn log I found the other exception.

3744-yarndetail-log.png

cid:image001.jpg@01D1A087.116D7430

And in the attempt log we have the exception detail

[FATAL] [HistoryEventHandlingThread] |yarn.YarnUncaughtExceptionHandler|: Thread Thread[HistoryEventHandlingThread,5,main] threw an Error.  Shutting down now...
java.lang.NoSuchMethodError: org.codehaus.jackson.map.ObjectMapper.setSerializationInclusion(Lorg/codehaus/jackson/map/annotate/JsonSerialize$Inclusion;)Lorg/codehaus/jackson/map/ObjectMapper;
  at org.apache.hadoop.yarn.webapp.YarnJacksonJaxbJsonProvider.configObjectMapper(YarnJacksonJaxbJsonProvider.java:59)
  at org.apache.hadoop.yarn.webapp.YarnJacksonJaxbJsonProvider.locateMapper(YarnJacksonJaxbJsonProvider.java:52)
  at org.codehaus.jackson.jaxrs.JacksonJsonProvider.writeTo(JacksonJsonProvider.java:501)
  at com.sun.jersey.api.client.RequestWriter.writeRequestEntity(RequestWriter.java:300)
  at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:204)
  at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:147)
  at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$TimelineJerseyRetryFilter$1.run(TimelineClientImpl.java:234)
  at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$TimelineClientConnectionRetry.retryOn(TimelineClientImpl.java:183)
  at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$TimelineJerseyRetryFilter.handle(TimelineClientImpl.java:245)
  at com.sun.jersey.api.client.Client.handle(Client.java:648)
  at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670)
  at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
  at com.sun.jersey.api.client.WebResource$Builder.post(WebResource.java:563)
  at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.doPostingObject(TimelineClientImpl.java:474)
  at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$1.run(TimelineClientImpl.java:323)
  at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$1.run(TimelineClientImpl.java:320)
  at java.security.AccessController.doPrivileged(Native Method)
  at javax.security.auth.Subject.doAs(Subject.java:422)
  at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
  at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.doPosting(TimelineClientImpl.java:320)
  at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.putEntities(TimelineClientImpl.java:305)
  at org.apache.tez.dag.history.logging.ats.ATSHistoryLoggingService.handleEvents(ATSHistoryLoggingService.java:346)
  at org.apache.tez.dag.history.logging.ats.ATSHistoryLoggingService.access$700(ATSHistoryLoggingService.java:53)
  at org.apache.tez.dag.history.logging.ats.ATSHistoryLoggingService$1.run(ATSHistoryLoggingService.java:190)
  at java.lang.Thread.run(Thread.java:745)
2016-04-27 13:02:23,212 [INFO] [HistoryEventHandlingThread] |util.ExitUtil|: Exiting with status -1
2016-04-27 13:02:23,214 [INFO] [Thread-3] |app.DAGAppMaster|: DAGAppMasterShutdownHook invoked
2016-04-27 13:02:23,214 [INFO] [Thread-3] |app.DAGAppMaster|: DAGAppMaster received a signal. Signaling TaskScheduler
2016-04-27 13:02:23,214 [INFO] [Thread-3] |rm.TaskSchedulerEventHandler|: TaskScheduler notified that iSignalled was : true
2016-04-27 13:02:23,376 [INFO] [ServiceThread:org.apache.tez.dag.app.web.WebUIService] |webapp.WebApps|: Registered webapp guice modules

We are using HDP 2.3.

Please help me in this.

Thanks,

Vijay

6 REPLIES 6

Re: problem in beeline query execution

Rising Star

How does your cluster look like (how many worker/master nodes, how is hive deployed)? Have you changed something in your environment? How are you submitting the query?

Re: problem in beeline query execution

New Contributor

Hi Marco Gaido,

Our cluster deployment is through ambari and we didn't change anything. The Query submission is via oozie workflow hive2 action and we are performing the operation on the habse link table.

Re: problem in beeline query execution

Rising Star

Then, it's probably a problem related to this JIRA: https://issues.apache.org/jira/browse/HBASE-13149. Can you upgrade to a newer version?

Re: problem in beeline query execution

New Contributor

Hi Marco Gaido,

upgrade to a newer version for what the HDP or the HBASE?

Re: problem in beeline query execution

New Contributor

I already tried solution posted on HBASE-13149:

3. You can also choose to replace the Jackson 1.8.8 jars in $HBASE_HOME/lib with 1.9.13 jars from your Hadoop lib directory. We have tested HBase 0.98 with Jackson 1.9.13.

But on HDP 2.3.1 i can see that jackson jars are already on 1.9.13, so its still not working for me.

-bash-4.1# ll /usr/hdp/current/hbase-client/lib/jackson- jackson-core-2.2.3.jar

jackson-core-asl-1.9.13.jar

jackson-jaxrs-1.9.13.jar

jackson-mapper-asl-1.9.13.jar

jackson-xc-1.9.13.jar

Also, for option:

2. Explore classpath isolation options (e.g. HADOOP-10893) or have your own classpath isolation strategy that works for you.

Could you please confirm it will not cause affect any other functionality in HDP ecosystem as a ripple effect.

Re: problem in beeline query execution

Rising Star

I think you might look at which version of the same library is used by hive and tez. It's likely that there is a version mismatch.. Maybe the easiest way to solve the issue would be an upgrade to a newer HDP version if you can do that

Don't have an account?
Coming from Hortonworks? Activate your account here