Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 7 Aug 2013 22:08:47 +0000 (UTC)
From: "Gary Helmling (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12660839.1375234807768.20584.1375913327969@arcas>
In-Reply-To: <JIRA.12660839.1375234807768@arcas>
References: <JIRA.12660839.1375234807768@arcas>
Subject: [jira] [Commented] (HBASE-9097) Set HBASE_CLASSPATH before rest of
 the classpath
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Helmling commented on HBASE-9097:
--------------------------------------

I'd also expect HBASE_CLASSPATH to override other classes/settings, so +1 from me.

The way Hadoop handled this is by sprouting another HADOOP_USER_CLASSPATH_FIRST env variable, which if not empty has HADOOP_CLASSPATH be added to the classpath prior to other libs (but still after HADOOP_CONF_DIR).  See MAPREDUCE-1938 for details.

Personally, I don't see the extra complication being worth it, but wanted to raise this alternate approach as an option.  For me, it makes sense to have HBASE_CLASSPATH precede everything, which also means potentially overriding the HBASE_CONF_DIR being used.
                
> Set HBASE_CLASSPATH before rest of the classpath
> ------------------------------------------------
>
>                 Key: HBASE-9097
>                 URL: https://issues.apache.org/jira/browse/HBASE-9097
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.98.0, 0.95.2, 0.94.11
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>         Attachments: hbase-9097-v0.patch
>
>
> We encountered this when one of the hadoop test jars (specifically hadoop-mapreduce-client-jobclient-2.0.0-cdh4.3.0-tests.jar, but that's beside the point) had an hdfs-site.xml. This clobbered the hdfs-site.xml that we included on the classpath via HBASE_CLASSPATH in hbase-env.sh, meaning the master didn't start in HA NN mode, because the proxy-provider wasn't found in the hdfs-site.xml from the test jar (even though it was in our config file) because that was the first resolution of that file.
> This should be a fairly simple fix in bin/hbase, but has some potentially wide-ranging effects on existing installs that just 'happen' to work.
> Generally, I'd expect things set on the HBASE_CLASSPATH to take precedence over anything else when starting the hbase daemon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira