[ 
https://issues.apache.org/jira/browse/HIVE-10436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

anna ken updated HIVE-10436:
----------------------------
    Description: closed  (was: Hi,

In Hadoop, while creating Table in hive i am getting stuck in below error

15/04/21 12:35:34 INFO log.PerfLogger: <PERFLOG method=Driver.run 
from=org.apache.hadoop.hive.ql.Driver>
15/04/21 12:35:34 INFO log.PerfLogger: <PERFLOG method=TimeToSubmit 
from=org.apache.hadoop.hive.ql.Driver>
15/04/21 12:35:34 INFO log.PerfLogger: <PERFLOG method=acquireReadWriteLocks 
from=org.apache.hadoop.hive.ql.Driver>
15/04/21 12:35:34 INFO lockmgr.DummyTxnManager: Creating lock manager of type 
org.apache.hadoop.hive.ql.lockmgr.zookeeper.ZooKeeperHiveLockManager
15/04/21 12:35:34 INFO zookeeper.ZooKeeper: Initiating client connection, 
connectString=dkhc3013.dcsg.com:2181,dkhc3010.dcsg.com:2181,dkhc3011.dcsg.com:2181
 sessionTimeout=600000 
watcher=org.apache.hadoop.hive.ql.lockmgr.zookeeper.ZooKeeperHiveLockManager$DummyWatcher@5b9e1cd4
15/04/21 12:35:34 DEBUG lockmgr.DummyTxnManager: Adding 
/incoming/mkt/gcdb.etl_master_account_pref to list of lock inputs
15/04/21 12:35:34 DEBUG lockmgr.DummyTxnManager: Adding database:mkt_incoming 
to list of lock outputs

After restart the zookeeper service i am able to successfully run the query,

But after some time again facing the same issue/error, I am stuck on the same 
error.

is there any solution to overcome this issue, or any tuning i can do for 
resolve this issue. ?

Please suggest on this.)
        Summary: closed  (was: DEBUG lockmgr.DummyTxnManager: Adding database 
:mkt_incoming to list of lock outputs)

> closed
> ------
>
>                 Key: HIVE-10436
>                 URL: https://issues.apache.org/jira/browse/HIVE-10436
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive, HiveServer2
>            Reporter: ankush
>              Labels: hadoop-2.0, hive, zookeeper
>
> closed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to