You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/02/04 17:22:00 UTC
[jira] [Commented] (HBASE-23794) Consider setting
-XX:MaxDirectMemorySize in the root Maven pom.xml file.
[ https://issues.apache.org/jira/browse/HBASE-23794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030004#comment-17030004 ]
Nick Dimiduk commented on HBASE-23794:
--------------------------------------
What's your suggested value here for the rank-and-file tests [~markrmiller]? You see where this might be added to our base pom in the {{hbase-surefire.argLine}} property?
It's quite possible we have {{LargeTest}} classes that attempt to verify our off-heap data pathways. You might have a look into how those test classes manage themselves before tweaking anything in this area.
> Consider setting -XX:MaxDirectMemorySize in the root Maven pom.xml file.
> ------------------------------------------------------------------------
>
> Key: HBASE-23794
> URL: https://issues.apache.org/jira/browse/HBASE-23794
> Project: HBase
> Issue Type: Test
> Reporter: Mark Robert Miller
> Priority: Minor
>
> -XX:MaxDirectMemorySize is an artificial governor on how much off heap memory can be allocated.
> It would be nice to specify explicitly because:
> # The default can vary by platform / jvm impl - some devs may see random fails
> # It's just a limiter, it won't pre allocate or anything
> # A test env should normally ensure a healthy limit as would be done in production
--
This message was sent by Atlassian Jira
(v8.3.4#803005)