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

Hadoop QA commented on AMBARI-18897:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12838998/AMBARI-18897.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 4 new 
or modified test files.

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

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

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9292//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9292//console

This message is automatically generated.

> HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-18897
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18897
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18897.patch
>
>
> /etc/hbase/conf/ contains core-site.xml and hdfs-site.xml which should not be 
> needed at all. But more importantly, when we change a setting in Ambari, they 
> do not get reflected in the hdfs-site.xml that is under the hbase conf 
> directory. Since there are more than 1 core-site.xml in the classpath, this 
> obviously causes issues since the changed configs are not picked up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to