ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13133) Hive Metastore did not start when Kerberized
Date Fri, 18 Sep 2015 16:05:06 GMT

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

Hudson commented on AMBARI-13133:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #3463 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3463/])
AMBARI-13133. Hive Metastore did not start when Kerberized (rlevas) (rlevas: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7bc58ac7c76bd5550d5794ec679860c7c0531e3c)
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_metastore.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/status_params.py
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_service.py
* ambari-server/src/test/python/stacks/2.1/HIVE/test_hive_metastore.py


> Hive Metastore did not start when Kerberized
> --------------------------------------------
>
>                 Key: AMBARI-13133
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13133
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>             Fix For: 2.2.0, 2.1.2
>
>         Attachments: AMBARI-13133_branch2.1_01.patch, AMBARI-13133_trunk_01.patch
>
>
> When starting up HiveMetastore under a Kerberized cluster, the following error occurs:
> {code}
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt /etc/security/keytabs/hive.service.keytab
hive/host1.company.com@REALM; ' returned 1. kinit: Keytab contains no suitable keys for hive/host1.company.com@REALM
while getting initial credentials
> {code}
> This happens when Hive Metastore and HiveServer2 principals are set up distinct from
each other.
> Hive Metastore is not using hive.metastore.kerberos.principal, but instead it uses hive.server2.authentication.kerberos.principal
> Also, the following references hive_conf_dir:
> https://github.com/apache/ambari/blob/release-2.1.1/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py#L119-L120
> In HDP2.3+ the following file content becomes UNSECURED
> /var/lib/ambari-agent/data/structured-out-status.json
> We need to either reference hive_server_conf_dir or set hive_conf_dir as hive_server_conf_dir
somewhere:
> https://github.com/apache/ambari/blob/release-2.1.1/ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/status_params.py#L90-L101
> *Solution*
> Since a kinit call here is unnecessary and the relevant configuration files are being
created properly.  Simply removing the kinit call (and related variabled) will fix the kinit
failure issue.
> For the hive_conf_dir issue, setting {{hive_conf_dir = hive_server_conf_dir}} in status_params.py,
solves the issue. 



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

Mime
View raw message