[
https://issues.apache.org/jira/browse/HADOOP-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089340#comment-15089340
]
Steve Loughran commented on HADOOP-12261:
-----------------------------------------
Catching up on this constructive discussion showing open source communities at
work, can I point out that this is something you can actually tune on the
command line,
{code}
mvn clean test "-Dmaven-surefire-plugin.argLine=-Xmx6G"
{code}
It's not something we need to change just yet, unless its critical everywhere
—and if we do change it, anyone who does want to try and build & test on 32
bits can still change the option to a value they can handle.
On Java 8 you'd want to turn off the permgen value too, just to avoid being
told off by the JVM for setting it.
> Surefire needs to make sure the JVMs it fires up fit within the memory
> available
> --------------------------------------------------------------------------------
>
> Key: HADOOP-12261
> URL: https://issues.apache.org/jira/browse/HADOOP-12261
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: test
> Affects Versions: 2.7.1
> Reporter: Alan Burlison
> Assignee: Alan Burlison
> Attachments: HADOOP-12261.001.patch
>
>
> hadoop-project/pom.xml sets maven-surefire-plugin.argLine to include
> -Xmx4096m. Allocating that amount of memory requires a 64-bit JVM, but on
> platforms with both 32 and 64-bit JVMs surefire runs the 32 bit version by
> default and tests fail to start as a result. "-d64" should be added to the
> command-line arguments to ensure a 64-bit JVM is always used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
