ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <>
Subject [jira] [Updated] (AMBARI-13133) Hive Metastore did not start when Kerberized
Date Thu, 17 Sep 2015 17:54:04 GMT


Robert Levas updated AMBARI-13133:
    Attachment: AMBARI-13133_trunk_01.patch

> Hive Metastore did not start when Kerberized
> --------------------------------------------
>                 Key: AMBARI-13133
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>         Attachments: 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/; ' returned 1. kinit: Keytab contains no suitable keys for hive/
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:
> 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
> *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,
solves the issue. 

This message was sent by Atlassian JIRA

View raw message