[
https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611143#comment-13611143
]
stack commented on HBASE-7904:
------------------------------
[~sseth]
bq. Using the config returned by MiniMRCluster is preferred to avoid similar
problems in the future. Am guessing "yarn.resourcemanager.address" and
"yarn.resourcemanager.scheduler.address" were set as a result of a similar
change.
Usually configs are out in xml files that we read into our context? The hbase
Configuration adds the hbase-*.xml files to its base set. If tests need
specific configs., we add them in xml and then make sure the Configuration
reads them in before test runs. What can't we do that in this case rather than
do this config. copy?
Yes, hbase tests run in //.
bq. mapred.local.dir set in HBaseTestingUtility will not have an affect on a
YARN cluster.
Fine.
Why we even specifying addresses? Why are there not defaults that just work in
say the standalone case so downstream projects don't even have to be concerned
w/ setting this stuff?
Thanks for the help on this one.
> Upgrade hadoop 2.0 dependency to 2.0.4-alpha
> --------------------------------------------
>
> Key: HBASE-7904
> URL: https://issues.apache.org/jira/browse/HBASE-7904
> Project: HBase
> Issue Type: Task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Critical
> Fix For: 0.95.0
>
> Attachments: 7904.txt, 7904-v2-hadoop-2.0.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, 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
