hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Srinivas Thunga <srinivas.thu...@gmail.com>
Subject Re: Concurrency issue, Setting hive.txn.manager to "org.apache.hadoop.hive.ql.lockmgr.DbTxnManager"
Date Tue, 07 Apr 2015 07:10:00 GMT
hi Mich,

Have you created the hive metastore? And can you please check the log for
hivemetastore

As i also faced this issue before.

And let me know

*Thanks & Regards,*

*Srinivas T*

On Tue, Apr 7, 2015 at 9:13 AM, Eugene Koifman <ekoifman@hortonworks.com>
wrote:

>  can you check that the schema in your metastore db has transaction
> related tables?
> You can find the list of tables in hive-txn-schema-0.14.0.mysql.sql, for
> example.
>
>   From: Mich Talebzadeh <mich@peridale.co.uk>
> Reply-To: "user@hive.apache.org" <user@hive.apache.org>
> Date: Monday, April 6, 2015 at 8:05 AM
> To: "user@hive.apache.org" <user@hive.apache.org>, "@Sanjiv Singh" <
> sanjiv.is.on@gmail.com>
> Subject: RE: Concurrency issue, Setting hive.txn.manager to
> "org.apache.hadoop.hive.ql.lockmgr.DbTxnManager"
>
>   Thanks Sanjiv.
>
>
>
> Unfortunately after resetting
>
>
>
> hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager
>
> and doing
>
>
>
> <property>
>
>   <name>hive.in.test</name>
>
>   <value>true</value>
>
>  </property>
>
>
>
>
>
> Still getting the same error message
>
>
>
> hive> show databases;
>
> FAILED: LockException [Error 10280]: Error communicating with the metastore
>
>
>
>
>
> Mich Talebzadeh
>
>
>
> http://talebzadehmich.wordpress.com
>
>
>
> *Publications due shortly:*
>
> *Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
> Coherence Cache*
>
>
>
> NOTE: The information in this email is proprietary and confidential. This
> message is for the designated recipient only, if you are not the intended
> recipient, you should destroy it immediately. Any information in this
> message shall not be understood as given or endorsed by Peridale Ltd, its
> subsidiaries or their employees, unless expressly so stated. It is the
> responsibility of the recipient to ensure that this email is virus free,
> therefore neither Peridale Ltd, its subsidiaries nor their employees accept
> any responsibility.
>
>
>
> *From:* @Sanjiv Singh [mailto:sanjiv.is.on@gmail.com
> <sanjiv.is.on@gmail.com>]
> *Sent:* 06 April 2015 15:21
> *To:* user@hive.apache.org
> *Subject:* Re: Concurrency issue, Setting hive.txn.manager to
> "org.apache.hadoop.hive.ql.lockmgr.DbTxnManager"
>
>
>
> Not sure ..It should work
>
> Try adding below configuration and then check..
>
>  <property>
>
>   <name>hive.in.test</name>
>
>   <value>true</value>
>
>  </property>
>
>
>
>
>   Regards
> Sanjiv Singh
> Mob :  +091 9990-447-339
>
>
>
> On Mon, Apr 6, 2015 at 7:21 PM, Mich Talebzadeh <mich@peridale.co.uk>
> wrote:
>
> Hi,
>
>
>
> I turned on concurrency for hive for DML with settings in hive-site.xml as
> follows:
>
>
>
> hive.support.concurrency=true
>
> hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager
>
> hive.compactor.initiator.on=true
>
> hive.compactor.worker.threads=2
>
> hive.support.concurrency=true
>
> hive.enforce.bucketing=true
>
> hive.exec.dynamic.partition.mode=nonstrict
>
>  Recycled connection to metastore and started hive server. Tried to query
> hive as follows:
>
>  hive> use asehadoop;
>
> FAILED: LockException [Error 10280]: Error communicating with the metastore
>
>
>
> Went back and set hive.txn.managerto default
>
> hive.txn.manager= org.apache.hadoop.hive.ql.lockmgr.DummyTxnManager
>
>
>
> and recycled again and all worked!
>
>
>
> Sounds like concurrency does not work or something extra I need to do?
>
>
>
> Thanks
>
>
>
> Mich Talebzadeh
>
>
>
> http://talebzadehmich.wordpress.com
>
>
>
> Publications due shortly:
>
> Creating in-memory Data Grid for Trading Systems with Oracle TimesTen and
> Coherence Cache
>
>
>
> NOTE: The information in this email is proprietary and confidential. This
> message is for the designated recipient only, if you are not the intended
> recipient, you should destroy it immediately. Any information in this
> message shall not be understood as given or endorsed by Peridale Ltd, its
> subsidiaries or their employees, unless expressly so stated. It is the
> responsibility of the recipient to ensure that this email is virus free,
> therefore neither Peridale Ltd, its subsidiaries nor their employees accept
> any responsibility.
>
>
>
>
>
>
>

Mime
View raw message