You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2017/07/26 00:04:09 UTC

[jira] [Closed] (HIVE-15403) LLAP: Login with kerberos before starting the daemon

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

Owen O'Malley closed HIVE-15403.
--------------------------------

> 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
>             Fix For: 2.2.0
>
>         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.4.14#64029)