hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <>
Subject [jira] [Commented] (HIVE-6488) Investigate TestBeeLineWithArgs
Date Wed, 12 Mar 2014 09:50:43 GMT


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.

2014-03-12 02:34:25,167 INFO  zookeeper.ClientCnxn (
- Opening socket connection to server localhost/ Will not attempt to authenticate
using SASL (Unable to locate a login configuration)
2014-03-12 02:34:25,177 WARN  zookeeper.ClientCnxn ( - Session 0x0
for server null, unexpected error, closing socket connection and attempting reconnect Connection refused
        at Method)
        at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(
        at org.apache.zookeeper.ClientCnxn$
2014-03-12 02:34:25,285 WARN  ZooKeeperHiveLockManager (
- 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(
        at org.apache.zookeeper.KeeperException.create(
        at org.apache.zookeeper.ZooKeeper.create(
        at org.apache.hadoop.hive.ql.lockmgr.zookeeper.ZooKeeperHiveLockManager.setContext(
        at org.apache.hadoop.hive.ql.lockmgr.DummyTxnManager.getLockManager(
        at org.apache.hadoop.hive.ql.lockmgr.DummyTxnManager.acquireLocks(
        at org.apache.hadoop.hive.ql.Driver.acquireReadWriteLocks(
        at org.apache.hadoop.hive.ql.Driver.runInternal(
        at org.apache.hive.service.cli.operation.SQLOperation.runInternal(
        at org.apache.hive.service.cli.operation.SQLOperation.access$100(
        at org.apache.hive.service.cli.operation.SQLOperation$
        at java.util.concurrent.Executors$
        at java.util.concurrent.FutureTask$Sync.innerRun(
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
        at java.util.concurrent.ThreadPoolExecutor$

> Investigate TestBeeLineWithArgs
> -------------------------------
>                 Key: HIVE-6488
>                 URL:
>             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

View raw message