You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/09/06 18:57:51 UTC

[jira] [Moved] (HADOOP-9938) Avoiding redundant Kerberos login for Zookeeper client in ActiveStandbyElector

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

Bikas Saha moved HDFS-5152 to HADOOP-9938:
------------------------------------------

    Component/s:     (was: security)
                 security
            Key: HADOOP-9938  (was: HDFS-5152)
        Project: Hadoop Common  (was: Hadoop HDFS)
    
> Avoiding redundant Kerberos login for Zookeeper client in ActiveStandbyElector
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-9938
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9938
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>            Reporter: Kai Zheng
>         Attachments: HDFS-5152.patch
>
>
> Based on the fix in HADOOP-8315, it's possible to deploy a secured HA cluster with SASL support for connection with Zookeeper. However it requires extra configuration for JAAS to initialize the Zookeeper client because the client will do another login in it even when ZKFC service actually has already passed the Kerberos login during its starting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira