[
https://issues.apache.org/jira/browse/HADOOP-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558292#action_12558292
]
stack commented on HADOOP-2578:
-------------------------------
Pardon me. My logic was, if the hbase-*.xml files have not been added to the
config. already, then go ahead and add them. I wasn't sure if it would work
(in fact, thinking on it, the config. by the time it gets out to the map task,
resource files will already have been read so my suggested test will likely
fail). I was asking you to try it/give an opinion.
Do your cluster members have an hbase-site.xml with customizations such as
hbase.master=master:60000 out on the cluster available off the CLASSPATH --
i.e. in $HADOOP_HOME/conf, or in $HADOOOP_CLASSPATH or in the job jar -- or
were the hbase customizations only present on the master or added when you set
up the job?
This issue has burned a few other folks in the past. Thanks for help w/ it.
Need to fix it.
Related, I've been trying to keep up a page on MR+hbase here:
http://wiki.apache.org/lucene-hadoop/Hbase/MapReduce. You might have some
edits/additions to make.
> HBaseConfiguration(Configuration c) constructor shouldn't overwrite passed
> conf with defaults
> ---------------------------------------------------------------------------------------------
>
> Key: HADOOP-2578
> URL: https://issues.apache.org/jira/browse/HADOOP-2578
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: Thomas Garner
>
> While testing out mapreduce with hbase, in the map portion of a task, the map
> would try to connect to an hbase master at localhost/127.0.0.1. The config
> passed to the hbaseconfiguration contained the necessary hbase configuration
> information, but I assume was being overwritten by the defaults in the config
> files during addResource, as commenting out addHbaseResources in the
> constructor fixed the symptom. I would expect the configs to be layered on
> top of each other, e.g. default, then site, then the config passed as a
> parameter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
