You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Prabhjyot Singh (JIRA)" <ji...@apache.org> on 2017/04/28 11:57:04 UTC
[jira] [Updated] (AMBARI-20888) wrong ZK parent node
(hbase-unsecure) getting configured as part of the jdbc(phoenix) URL on
ubuntu secured cluster
[ https://issues.apache.org/jira/browse/AMBARI-20888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prabhjyot Singh updated AMBARI-20888:
-------------------------------------
Assignee: Prabhjyot Singh
Status: Patch Available (was: Open)
> wrong ZK parent node (hbase-unsecure) getting configured as part of the jdbc(phoenix) URL on ubuntu secured cluster
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-20888
> URL: https://issues.apache.org/jira/browse/AMBARI-20888
> Project: Ambari
> Issue Type: Bug
> Reporter: Prabhjyot Singh
> Assignee: Prabhjyot Singh
>
> wrong ZK parent node (hbase-unsecure) getting configured as part of the jdbc(phoenix) URL on ubuntu secured cluster the jdbc(phoenix) url was getting appended as /hbase-unsecure which is not correct
> If you check the hbase-site.xml
> <property>
> <name>zookeeper.znode.parent</name>
> <value>/hbase-secure</value>
> </property>
> I think how the phoenix URL is being constructed is not consistent across the configs and we need to see why. On some of the other platforms, I have seen it getting configured correctly (for e.g. Centos6 secured wire-encrypted)
> Options
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)