hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-15403) LLAP: Login with kerberos before starting the daemon
Date Fri, 09 Dec 2016 20:34:58 GMT

     [ https://issues.apache.org/jira/browse/HIVE-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prasanth Jayachandran updated HIVE-15403:
-----------------------------------------
    Attachment: HIVE-15403.2.patch

updated comment

> LLAP: Login with kerberos before starting the daemon
> ----------------------------------------------------
>
>                 Key: HIVE-15403
>                 URL: https://issues.apache.org/jira/browse/HIVE-15403
>             Project: Hive
>          Issue Type: Bug
>          Components: llap
>    Affects Versions: 2.2.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Critical
>         Attachments: HIVE-15403.1.patch, HIVE-15403.2.patch
>
>
> In LLAP cluster, if some of the nodes are kinit'ed with some user (other than default
hive user) and some nodes are kinit'ed with hive user, both will end up in different paths
under zk registry and may not be reported by the llap status tool. The reason for that is
when creating zk paths we use UGI.getCurrentUser() but current user may not be same across
all nodes (someone has to do global kinit). Before bringing up the daemon, if security is
enabled each daemons should login based on specified kerberos principal and keytab for llap
daemon service and update the current logged in user. 



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

Mime
View raw message