[
https://issues.apache.org/jira/browse/HIVE-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931592#comment-13931592
]
Jason Dere commented on HIVE-6488:
----------------------------------
Looks like HS2 is continually trying/failing to connect to a zookeeper instance
at a default port 2181. Not sure when this started occurring or whether the
root cause of this needs to be fixed. Creating a zookeeper instance and
configuring the tests to use it allows this test to pass in under a minute.
{noformat}
2014-03-12 02:34:25,167 INFO zookeeper.ClientCnxn
(ClientCnxn.java:logStartConnect(966)) - Opening socket connection to server
localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (Unable
to locate a login configuration)
2014-03-12 02:34:25,177 WARN zookeeper.ClientCnxn (ClientCnxn.java:run(1089))
- Session 0x0 for server null, unexpected error, closing socket connection and
attempting reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:599)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1068)
2014-03-12 02:34:25,285 WARN ZooKeeperHiveLockManager
(ZooKeeperHiveLockManager.java:setContext(121)) - Unexpected ZK exception when
creating parent node /hive_zookeeper_namespace
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode =
ConnectionLoss for /hive_zookeeper_namespace
at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
at
org.apache.hadoop.hive.ql.lockmgr.zookeeper.ZooKeeperHiveLockManager.setContext(ZooKeeperHiveLockManager.java:117)
at
org.apache.hadoop.hive.ql.lockmgr.DummyTxnManager.getLockManager(DummyTxnManager.java:74)
at
org.apache.hadoop.hive.ql.lockmgr.DummyTxnManager.acquireLocks(DummyTxnManager.java:103)
at
org.apache.hadoop.hive.ql.Driver.acquireReadWriteLocks(Driver.java:840)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1046)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:884)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:879)
at
org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:139)
at
org.apache.hive.service.cli.operation.SQLOperation.access$100(SQLOperation.java:62)
at
org.apache.hive.service.cli.operation.SQLOperation$1.run(SQLOperation.java:168)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
{noformat}
> Investigate TestBeeLineWithArgs
> -------------------------------
>
> Key: HIVE-6488
> URL: https://issues.apache.org/jira/browse/HIVE-6488
> Project: Hive
> Issue Type: Bug
> Reporter: Brock Noland
> Priority: Blocker
>
> TestBeeLineWithArgs started taking many, many hours and eventually timing out
> which is one cause of precommit runs taking a long time. For now I have
> skipped it in for precommit tests so we should figure out what is going on so
> we can re-enable the test.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
