[
https://issues.apache.org/jira/browse/HBASE-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168755#comment-13168755
]
Joern Kottmann commented on HBASE-3465:
---------------------------------------
Sounds like that will fix the issues, but I don't know if it will have any
other consequences.
I more or less did set the HADOOP_HOME and other environment variables
accidentally and just really wonder why that disables the ganglia monitoring.
As far as I understand that is only needed for features I do not use anyway.
Maybe Ted or Alejandro can comment here if the suggested fix would cause any
issues.
> Hbase should use a HADOOP_HOME environment variable if available.
> -----------------------------------------------------------------
>
> Key: HBASE-3465
> URL: https://issues.apache.org/jira/browse/HBASE-3465
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.0
> Reporter: Ted Dunning
> Assignee: Alejandro Abdelnur
> Fix For: 0.92.0
>
> Attachments: a1-HBASE-3465.patch
>
>
> I have been burned a few times lately while developing code by having the
> make sure that the hadoop jar in hbase/lib is exactly correct. In my own
> deployment, there are actually 3 jars and a native library to keep in sync
> that hbase shouldn't have to know about explicitly. A similar problem arises
> when using stock hbase with CDH3 because of the security patches changing the
> wire protocol.
> All of these problems could be avoided by not assuming that the hadoop
> library is in the local directory. Moreover, I think it might be possible to
> assemble the distribution such that the compile time hadoop dependency is in
> a cognate directory to lib and is referenced using a default value for
> HADOOP_HOME.
> Does anybody have any violent antipathies to such a change?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
