You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/06/04 21:37:00 UTC

[jira] [Work logged] (HIVE-13491) Testing : log thread stacks when metastore fails to start

     [ https://issues.apache.org/jira/browse/HIVE-13491?focusedWorklogId=441538&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-441538 ]

ASF GitHub Bot logged work on HIVE-13491:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Jun/20 21:36
            Start Date: 04/Jun/20 21:36
    Worklog Time Spent: 10m 
      Work Description: belugabehr closed pull request #71:
URL: https://github.com/apache/hive/pull/71


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 441538)
    Time Spent: 20m  (was: 10m)

> Testing  : log thread stacks when metastore fails to start
> ----------------------------------------------------------
>
>                 Key: HIVE-13491
>                 URL: https://issues.apache.org/jira/browse/HIVE-13491
>             Project: Hive
>          Issue Type: Bug
>          Components: Test, Testing Infrastructure
>            Reporter: Thejas Nair
>            Assignee: Thejas Nair
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.3.0, 2.1.0
>
>         Attachments: HIVE-13491.1.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Many tests are failing in ptest2 because metastore fails to startup in the expected time.
> There is not enough information to figure out why the metastore startup failed/got hung in the hive.log file. Printing the thread dumps when that happens would be useful for finding the root cause.
> The stack in test failure looks like this -
> {code}
> java.net.ConnectException: Connection refused
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> 	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:198)
> 	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> 	at java.net.Socket.connect(Socket.java:579)
> 	at org.apache.hadoop.hive.metastore.MetaStoreUtils.loopUntilHMSReady(MetaStoreUtils.java:1208)
> 	at org.apache.hadoop.hive.metastore.MetaStoreUtils.startMetaStore(MetaStoreUtils.java:1195)
> 	at org.apache.hadoop.hive.metastore.MetaStoreUtils.startMetaStore(MetaStoreUtils.java:1177)
> 	at org.apache.hadoop.hive.thrift.TestHadoopAuthBridge23.setup(TestHadoopAuthBridge23.java:153)
> 	at org.apache.hadoop.hive.thrift.TestHadoopAuthBridge23.testMetastoreProxyUser(TestHadoopAuthBridge23.java:241)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)