[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624105#comment-13624105
]
Jonathan Hsieh commented on HBASE-8258:
---------------------------------------
bq. Are you saying that we fix the problems in HBase assuming
hadoop-2.0.2-alpha as the underlying hadoop version?
Yes. Its been what this build has been broken against for a long time so let's
get that fixed first. Haven't tried 2.0.3 yet, but after this gets fixed we can
go there. *One problem at a time and ideally per jira.*
bq. So let's say that we identify two or three configs. We should then change
copyConfigurationValues to be more restrictive in copying?
Experiment was already done, see [1] -- yarn.resourcemanager.scheduler.address,
yarn.resourcemanager.address were the main ones.
That lead to the follow up questions, which lead me to see that the whole
copying stuff is moot.
bq. On the first one, as per the last hadoopQA run without the fixes with
hadoop-2.0.4-SNAPSHOT
(https://issues.apache.org/jira/browse/HBASE-8258?focusedCommentId=13621696&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13621696),
almost all of the mapreduce tests failed.
I'm going to ignore tests run against a hadoop SNAPSHOT.
bq. Stack, are you suggesting that we should depend on 2.0.4-alpha sooner
rather than later, maybe even check with 2.0.4-SNAPSHOT on a periodic basis
until 2.0.4-alpha is released?
I think he means that not fixing this until 2.0.4 comes out is not a good idea,
but I'll let him answer.
[1]
https://issues.apache.org/jira/browse/HBASE-8258?focusedCommentId=13623739&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13623739
> 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
