[
https://issues.apache.org/jira/browse/AMBARI-15692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229351#comment-15229351
]
Hudson commented on AMBARI-15692:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4608 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4608/])
AMBARI-15692 : AMS-HBase should explicitly set its HBASE_HOME path (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5060b4f8c13d3746d72138324ad7cbf609462338])
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
*
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
> AMS-HBase should explicitly set its HBASE_HOME path
> ---------------------------------------------------
>
> Key: AMBARI-15692
> URL: https://issues.apache.org/jira/browse/AMBARI-15692
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.2.2
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Fix For: 2.4.0
>
> Attachments: AMBARI-15692.patch
>
>
> AMS-Collector host had the environment variable HBASE_HOME=/usr/lib/hbase
> defined somewhere in the system. AMS user somehow inherited this environment
> variable. When AMS-Collector started, he would start the embedded HBase which
> would use the incorrect environment variable and failed to start
> (/usr/lib/hbase was missing many JARs).
> AMS-HBase's hbase-env.sh script should explicitly set the HBASE_HOME to its
> own path and not fail due to some incorrect environment variable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
