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

Hudson commented on AMBARI-18897:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6031 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6031/])
AMBARI-18897. HBase conf directory should not have a copy of (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b5779fe6dca4db7df15abd905ef4b3dfae9d2c03])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json
* (edit) 
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py
* (edit) 
ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_regionserver.py
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/constants.py
* (edit) 
ambari-server/src/test/python/stacks/2.0.6/HBASE/test_phoenix_queryserver.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_client.py


> 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