You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/04/05 02:31:25 UTC
[jira] [Commented] (AMBARI-15692) AMS-HBase should explicitly set
its HBASE_HOME path
[ https://issues.apache.org/jira/browse/AMBARI-15692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225378#comment-15225378 ]
Hadoop QA commented on AMBARI-15692:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12796877/AMBARI-15692.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6187//console
This message is automatically generated.
> 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)