hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naveen (JIRA)" <>
Subject [jira] [Commented] (HIVE-6893) out of sequence error in HiveMetastore server
Date Tue, 15 Apr 2014 14:18:16 GMT


Naveen commented on HIVE-6893:

Mestastore is running as a standalone process/service outside the HS2 JVM. This issue was
seen after the following occured (there is no indication of a problem prior)
1) Upgrade the HMS DB (mysql)
2) Running with slightly newer version of HUE.
3) About 15 parallel beeswax sessions to HS2 each running a query.

We haven't been able to reproduce this in-house using a JDBC Client that spins off threads
that connect to HS2, run a query & exit. 

We suspected that it was one of the two causes
1) Socket timeouts during read by parallel invocations between HS2 (HMS Client) & HMS.

2) Concurrency issues in HMS on invocations to HMS.

After noticing Socket timeout exceptions in the HS2 logs, we had the customer increase the
socket read timeouts from 90s to 120s. Did not help, but also the hive logs indicate that
the "out of sequence" errors occurred first then the socket  timeouts, pretty far apart in
time. So the socket read timeout is not likely the root cause.

It must be concurrent access to the HMS by multiple beeswax sessions thats causing this issue.

Hope this helps.

> out of sequence error in HiveMetastore server
> ---------------------------------------------
>                 Key: HIVE-6893
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 0.12.0
>            Reporter: Romain Rigaux
> Calls listing databases or tables fail. It seems to be a concurrency problem.
> {code}
> 014-03-06 05:34:00,785 ERROR hive.log: org.apache.thrift.TApplicationException: get_databases
failed: out of sequence response
>         at org.apache.thrift.TServiceClient.receiveBase(
>         at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Client.recv_get_databases(
>         at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Client.get_databases(
>         at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.getDatabases(
>         at
>         at org.apache.hive.service.cli.session.HiveSessionImpl.getSchemas(
>         at sun.reflect.GeneratedMethodAccessor323.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>         at java.lang.reflect.Method.invoke(
>         at org.apache.hive.service.cli.session.HiveSessionProxy$
>         at Method)
>         at
>         at
>         at org.apache.hadoop.hive.shims.HadoopShimsSecure.doAs(
>         at org.apache.hive.service.cli.session.HiveSessionProxy.invoke(
>         at com.sun.proxy.$Proxy9.getSchemas(Unknown Source)
>         at org.apache.hive.service.cli.CLIService.getSchemas(
>         at org.apache.hive.service.cli.thrift.ThriftCLIService.GetSchemas(
>         at org.apache.hive.service.cli.thrift.TCLIService$Processor$GetSchemas.getResult(
>         at org.apache.hive.service.cli.thrift.TCLIService$Processor$GetSchemas.getResult(
>         at org.apache.thrift.ProcessFunction.process(
>         at org.apache.thrift.TBaseProcessor.process(
>         at org.apache.hive.service.cli.thrift.TSetIpAddressProcessor.process(
>         at org.apache.thrift.server.TThreadPoolServer$
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> {code}

This message was sent by Atlassian JIRA

View raw message