[
https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620462#comment-13620462
]
Siddharth Seth commented on HBASE-7904:
---------------------------------------
bq. This issue started out as an incompability issue (see original Ted Yu
comments at head of issue)
If this was about MiniMRCluster being deprecated, the replacement is
MiniMRClientClusterFactory which exists in branch-1 as well. Don't think this
is an incompatible change. If using the new interface,
MiniMRClientCluster.getConfig() can be used instead of
MiniMRCluster.createJobConf().
bq. Yes, hbase tests can be run in parallel: e.g. TestTableMapReduce and
TestHFileOutputFormat run at same time. Our surefire runs our test suite by
firing off N JVMs each running a distinct, long-running test.
Alright. So no parallel tests against a single cluster, but multiple clusters
can run at the same time since these two test classes spin up their own
clusters. MAPREDUCE-5083 becomes important to prevent the clusters clobbering
each other. Will pull that into the 2.0.4-alpha branch.
The summary posted over at YARN-449 (with these additions) should be enough to
get the hbase mapreduce tests passing. I'm guessing the HBase specific changes
will eventually make it in via separate jiras.
> Make mapreduce jobs pass based on 2.0.4-alpha
> ---------------------------------------------
>
> Key: HBASE-7904
> URL: https://issues.apache.org/jira/browse/HBASE-7904
> Project: HBase
> Issue Type: Task
> Components: mapreduce
> Reporter: Ted Yu
> Priority: Critical
> Attachments: 7904-addendum.txt, 7904.txt, 7904-v2-hadoop-2.0.txt,
> 7904-v2.txt, 7904-v4-hadoop-2.0.txt, 7904-v4.txt, 7904-v4.txt,
> 7904-v5-hadoop-2.0.txt, 7904-v5.txt, 7904-v6-hadoop-2.0.txt,
> 7904-v7-hadoop-2.0.txt, 7904-v8-hadoop-2.0.txt, 7904-v8.txt,
> 7904-v9-hadoop-2.0.txt, 7904-v9.txt, hbase-7904-v3.txt
>
>
> 2.0.3-alpha has been released.
> We should upgrade the dependency.
--
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
