You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Krisztian Kasa (JIRA)" <ji...@apache.org> on 2018/10/29 07:41:00 UTC
[jira] [Updated] (AMBARI-24838) Infra Manager: zookeper connection
string
[ https://issues.apache.org/jira/browse/AMBARI-24838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Krisztian Kasa updated AMBARI-24838:
------------------------------------
Priority: Blocker (was: Major)
> Infra Manager: zookeper connection string
> -----------------------------------------
>
> Key: AMBARI-24838
> URL: https://issues.apache.org/jira/browse/AMBARI-24838
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
> Affects Versions: 2.8.0
> Reporter: Krisztian Kasa
> Assignee: Krisztian Kasa
> Priority: Blocker
> Fix For: 2.8.0
>
>
> Infra Manager can not connect to zookeeper if it is installed into a node where there is no zookeeper server instance, or the local instance is down.
> * This is caused by that the infra manager stack code does not set the zookeeper quorum and the CloudSolrClient falls back to localhost:2181
> * Also the builder which is used for construct an org.apache.solr.client.solrj.impl.CloudSolrClient instance is deprecated: it does not handle the zookeper connection string fromat which sould be set in the stack code.
> {code}
> zkhost0:port[,zkhost1:port...zkhostn:port][/solr_znode]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)