[
https://issues.apache.org/jira/browse/MAPREDUCE-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189606#comment-13189606
]
Hitesh Shah commented on MAPREDUCE-3654:
----------------------------------------
In the TestTableMapReduce test, I ended up doing something along the lines of:
table.getConfiguration().set("mapreduce.framework.name", "yarn");
job = new Job(table.getConfiguration(), "process column contents");
to get around the clientprovider issue which seemed to have the test run
successfully but I could not completely verify as there are no logs generated
even though the hbase/hadoop log levels are set to debug. However, the above is
in any case not the correct solution.
When submitting a job to a cluster, the assumption would be to use the relevant
client-side aspects of the cluster's configuration. However in the hbase test,
what is happening is that the job and htable objects are being initialized via
HbaseTestingUtility.getConfiguration(). The test framework encapsulates the
dfs/mr clusters but currently it does set internal configs like the jobtracker
address for the test to work. It would need to change to probably use the new
cluster factory created as part of MAPREDUCE-3169 to switch between mr1/mr2 and
also likely set some config values if the job configs are not initialized using
the mrCluster's configuration ( such as jobtracker address for MR1 and for MR2,
yarn's resource/node mgr addresses in addition to the framework name being set
to yarn).
> MiniMRYarnCluster should set MASTER_ADDRESS to "local"
> ------------------------------------------------------
>
> Key: MAPREDUCE-3654
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3654
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, test
> Affects Versions: 0.23.1
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Critical
> Attachments: MAPREDUCE-3654.patch
>
>
> I needed to make the attached change in order for MiniMRCluster based HBase
> tests to get past job client initialization.
--
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
