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

Olivér Szabó updated AMBARI-22860:
----------------------------------
    Fix Version/s:     (was: 3.0.0)
                   2.7.0

> Support external zookeeper for Infra Solr and Log Search
> --------------------------------------------------------
>
>                 Key: AMBARI-22860
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22860
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-infra
>    Affects Versions: 2.7.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Supporting external ZooKeeper from Infra Solr.
> Security: If Infra Solr is secured we can assume that ZooKeeper is secure as 
> well, same for non-secured environment
> Addition to that:
> Ambari Infra (Solr) 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:
>  * 
> {{ambari/ambari-logsearch/ambari-logsearch-solr-client/src/main/resources/solrCloudCli.sh}}
>  must be changed to set 
> {{-Dzookeeper.sasl.client.username=<ZOOKEEPER_PRINCPAL_NAME>}}
>  * {{-Dzookeeper.sasl.client.username=<ZOOKEEPER_PRINCPAL_NAME>}} should be 
> added to{{SOLR_OPTS}}



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

Reply via email to