hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Chanan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5529) MR test failures becuase MALLOC_ARENA_MAX is not set
Date Thu, 08 Mar 2012 06:01:02 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225023#comment-13225023

Gregory Chanan commented on HBASE-5529:

I don't think we need to add it to hbase-env.sh.  The issue (at least what I've experienced)
is with the mapreduce containers.  So we need it in the surefire config when running unit
tests, but when running the jobs normally, hadoop already has the configuration, because of

If we run into these errors in another area of hbase, we can add it at that time.
> MR test failures becuase MALLOC_ARENA_MAX is not set
> ----------------------------------------------------
>                 Key: HBASE-5529
>                 URL: https://issues.apache.org/jira/browse/HBASE-5529
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce, test
>    Affects Versions: 0.92.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>            Priority: Minor
>         Attachments: HBASE-5529-to92.patch, HBASE-5529-trunk.patch
> When running unit tests on CentOS 6 I get a bunch of unit test failures in mapreduce-related
tests due to:
> 2012-03-03 00:14:18,776 WARN  [Container Monitor]
> monitor.ContainersMonitorImpl$MonitoringThread(436): Container
> [pid=21446,containerID=container_1330762435849_0002_01_000001] is
> running beyond virtual memory limits. Current usage: 223.1mb of 2.0gb
> physical memory used; 6.9gb of 4.2gb virtual memory used. Killing
> container.
> Note: this also came up in the mapreduce project. See: https://issues.apache.org/jira/browse/MAPREDUCE-3933
> Patch coming shortly

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message