[
https://issues.apache.org/jira/browse/AMBARI-20888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994374#comment-15994374
]
Hudson commented on AMBARI-20888:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7411 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7411/])
AMBARI-20888. wrong ZK parent node (hbase-unsecure) getting configured (grvngr:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4134bbfb0a2c02b81f66dbed954fb9495ef969f2])
* (edit)
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py
> 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
> Fix For: 2.5.1
>
> Attachments: AMBARI-20888_trunk_v1.patch
>
>
> 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)
