ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19534) Hive Metastore process cannot be determined to be up and listening on the network
Date Fri, 13 Jan 2017 17:08:26 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-19534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822007#comment-15822007
] 

Siddharth Wagle commented on AMBARI-19534:
------------------------------------------

Pushed to 2.5 and trunk.

> Hive Metastore process cannot be determined to be up and listening on the network
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-19534
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19534
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19534.patch
>
>
> Hive Metastore process cannot be determined to be up and listening on the network , alert
is on for same for long time .
> hive metastore log is having following error:
> 2017-01-11 19:59:00,171 ERROR [pool-7-thread-200]: server.TThreadPoolServer (TThreadPoolServer.java:run(297))
- Error occurred during processing of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: Invalid
status -128
> In health check command, HIVE_CONF_DIR is being set to the conf.server directory, which
ambari-qa user doesn't have access to. It should be set to /usr/hdp/current/hive-metastore/conf
instead.



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

Mime
View raw message