hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8258) Make mapreduce tests pass on hadoop2
Date Fri, 05 Apr 2013 23:47:15 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624191#comment-13624191

Devaraj Das commented on HBASE-8258:

bq. I suggest sooner so if any issues in hdfs/mr/yarn, we can help out our parent project
by surfacing them quicker (For example, I don't mind shipping a 0.95.x "Development" Series
release against a hadoop SNAPSHOT; I don't see it as a problem given the quick decay half-life
of 0.95.x release).

Hmm.. fair point, [~stack], given 0.95.x is not meant for production. [~jmhsieh], what do
you think about this suggestion. The vmem issues you encountered won't happen with hadoop-2.0.4
since the YARN fixes are committed to not do vmem checks by default.
Your patch AFAICT is not sufficient to ride HBase over the hadoop-2.0.3 / 2.0.4 releases.
We need some variant of Ted's patch for having HBase pass the unit tests successfully over
the 2.0.4 release.. (otherwise we will have this saga all over again in a few weeks).
> 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
>         Attachments: 8258-plain.txt, 8258-v1-hadoop-2.0.txt, 8258-v2-hadoop-2.0.txt,
8258-v4-hadoop-2.0.txt, hbase-8258-simple.patch
> 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

View raw message