ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-22847) HBase should handle a customized Zookeeper service principal name
Date Mon, 29 Jan 2018 23:39:07 GMT

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

Robert Levas updated AMBARI-22847:
----------------------------------
    Fix Version/s:     (was: 3.0.0)
                   2.7.0

> HBase should handle a customized Zookeeper service principal name
> -----------------------------------------------------------------
>
>                 Key: AMBARI-22847
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22847
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Critical
>              Labels: kerberos, pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> HBase should handle a customized Zookeeper service principal name.
> Currently this is not supported due to hardcoded and implicit values expecting the Zookeeper
service principal name to be {{zookeeper/_HOST}} as opposed to something like {{zookeeper-mycluster/_HOST}}.
> The following changes need to be made:
>  * Add {{-Dzookeeper.sasl.client.username=<ZOOKEEPER_PRINCPAL_NAME>}} to {{HBASE_OPTS}} in {{hbase-env/template}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message