[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621618#comment-13621618
]
Jonathan Hsieh commented on HBASE-8258:
---------------------------------------
Hm.. you are right -- on my setup on April 1 (before the revert of HBASE-7904)
trunk runs I have 21 tests in org.apache.hadoop.hbase.mapreduce. The
TestImportExport cases are actually flaking between failure and non being
reported (hanging?).
Here's my theory from a previous attempt. I believe several months ago I
narrowed the problem to hbase and the yarn/mr2 instances writing to different
hdfs's. I might have this flipped but it was something like hbase would write
and read from a the minihdfs cluster's hfds. So a table would be written to
the minihdfs. The mr2 export job would read from hbase, but write data to a
its different "local" file system. The import job would check for files in its
minihdfs cluster and not find them and then fail.
I'm in the process of confirming if this is still the case.
> Make mapreduce tests pass on hadoop2
> ------------------------------------
>
> Key: HBASE-8258
> URL: https://issues.apache.org/jira/browse/HBASE-8258
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Reporter: stack
> Priority: Blocker
> Fix For: 0.95.1
>
>
> HBASE-7904 was a first attempt at making this work but it got lost in the
> weeds.
> This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o
> breaking mapreduce on hadoop1)
--
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
