[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623907#comment-13623907
]
Jonathan Hsieh commented on HBASE-8258:
---------------------------------------
bq. 2.0.4 has some fixes that impact HBase tests (MAPREDUCE-5083, YARN-470 at
the least). I think we should wait for the release to happen before we do
anything more on this issue.
When it comes out we deal with it.
The isolation of the particular relevant yarn configs demonstrate that the vmem
stuff is red herring and unrelated as of hadoop 2.0.2.
bq. This (the need to copy configuration values) was discovered and introduced
way back in HBASE-6601. Ted's patch that had the reference to "merge" made it
so that all MR tests could get all the (updated) configuration key/vals. In
reality, copyConfigurationValues alone is sufficient. Ted's current patch has
it that way (all MR tests get the updated configs via copyConfigurationValues).
I think the javadoc comment on copyConfigurationValues is already a nice
document. Maybe, we could enhance that a bit..
copyConfigurationValues seems overly broad and doesn't expose the root cause.
You also skipped the last two questions -- without getting to the root, this
still doesn't explain why it works for other hbase-mr tests and not here, and
how to make it so that any other mr tests doesn't have to have a special
copyConfiguraitonValues equivalent call.
> 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
>
>
> 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
