[
https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611328#comment-13611328
]
stack commented on HBASE-7904:
------------------------------
[~sseth]
bq. I'm sure HBase has similar client configs - which need to be loaded to
access the MiniHBaseCluster. How are clients expected to use this ?
Makes sense now.
bq. To allow parallel MiniClusters (different ports).
// clusters are default?
All I want to do is launch a job, do I need know addresses (if no addresses,
use default localhost?)
Above is not important.
bq. OOM, they're being killed by YARN resource monitoring.
I see by reading over in MR-5083, that it is a vmem limit. Can I up the vmem
limit now w/o waiting on mr-5083 by setting some configs on minimr?
bq. After MR-5083 is committed (and snapshot published to mvn), can we trigger
another run of the HBase tests - that should eliminate potential random
failures caused by parallel tests.
Yes. Of course.
Thanks.
> 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.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
