[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626800#comment-13626800
]
Jonathan Hsieh commented on HBASE-8258:
---------------------------------------
Without the memory-mb and vmem-pmem lines, yarn jobs were failing out with ~250
mb physical memory and 6.2gb vmem. I haven't been using the same memory
constraints on my test runs, but since these are the only lines that could
affect those tests. [~apurtell] do you have an alternate suggestion? (2x vmem
seems reasonable)
That amount of vmem implies that either our client uses way too many threads
(allocating vmem for each threads' stack) or there is something funny in yarn.
> 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-8258.simple.v2.patch, hbase-8258.simple.v3.patch,
> hbase-8258.simple.v4.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
