ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20888) wrong ZK parent node (hbase-unsecure) getting configured as part of the jdbc(phoenix) URL on ubuntu secured cluster
Date Fri, 28 Apr 2017 12:57:04 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-20888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988769#comment-15988769
] 

Hadoop QA commented on AMBARI-20888:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12865531/AMBARI-20888_trunk_v1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:red}-1 core tests{color}.  The test build failed in [ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/11526//artifact/patch-work/testrun_ambari-server.txt]


Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11526//console

This message is automatically generated.

> 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
>         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)

Mime
View raw message