hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yogendra reddy <>
Subject RE: hive transactions
Date Thu, 04 Dec 2014 02:28:28 GMT
Thanks Alan, I'm able to see TXNS table and yes I have upgraded from 0.13 to 0.14. 

any idea as to wht else might cause this issue?


-----Original Message-----
From: "Alan Gates" <>
Sent: ‎12/‎3/‎2014 9:51 AM
To: "" <>
Subject: Re: hive transactions

Usually this means the metastore database was not properly upgraded.  You can check this by
logging into your RDBMS and listing all the tables.  If you see a table named TXNS then the
proper tables exist.  

Did you install Hive 0.14 fresh or upgrade from a previous version?  If you upgraded did you
run the upgrade scripts?  In the Hive 0.12 to Hive 0.13 upgrade script it calls hive-txn-schema-0.13.0.mysql.sql,
which will create these tables.  If you're upgrading from 13 to 14 there shouldn't be a need
to create the tables.


yogendra reddy
November 30, 2014 at 21:19
Hi All,

I'm caught up with the error pasted below after trying to use hive transaction feature.I have
followed this wiki to set required configuration.

set hive.exec.dynamic.partition.mode=nonstrict;
set hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager;
set hive.compactor.initiator.on=true;
set hive.compactor.worker.threads=1;

After setting the above I just ran this command "describe formatted acidtest;"
any pointers as to why this occurs?

FAILED: Error in acquiring locks: Error communicating with the metastore
14/12/01 05:02:05 ERROR ql.Driver: FAILED: Error in acquiring locks: Error communicating with
the metastore
org.apache.hadoop.hive.ql.lockmgr.LockException: Error communicating with the metastore
        at org.apache.hadoop.hive.ql.lockmgr.DbLockManager.lock(
        at org.apache.hadoop.hive.ql.lockmgr.DbTxnManager.acquireLocks(
        at org.apache.hadoop.hive.ql.Driver.acquireLocksAndOpenTxn(
        at org.apache.hadoop.hive.ql.Driver.runInternal(
        at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(
        at org.apache.hadoop.hive.cli.CliDriver.processCmd(
        at org.apache.hadoop.hive.cli.CliDriver.processLine(
        at org.apache.hadoop.hive.cli.CliDriver.executeDriver(
        at org.apache.hadoop.hive.cli.CliDriver.main(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.apache.hadoop.util.RunJar.main(
Caused by: org.apache.thrift.TApplicationException: Internal error processing lock
        at org.apache.thrift.TServiceClient.receiveBase(
        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Client.recv_lock(
        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Client.lock(
        at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.lock(
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(
        at com.sun.proxy.$Proxy9.lock(Unknown Source)
        at org.apache.hadoop.hive.ql.lockmgr.DbLockManager.lock(
        ... 17 more

p.s : Before setting the transaction specific properties I was able to run hive queries successfully



Sent with Postbox

NOTICE: This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended recipient, you are hereby
notified that any printing, copying, dissemination, distribution, disclosure or forwarding
of this communication is strictly prohibited. If you have received this communication in error,
please contact the sender immediately and delete it from your system. Thank You.
View raw message