[
https://issues.apache.org/jira/browse/HADOOP-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639263#comment-14639263
]
Colin Patrick McCabe commented on HADOOP-12261:
-----------------------------------------------
On a 32-bit machine with a traditional 50/50 kernel/usermode split, 2 GB is the
most any process can have. Are we comfortable cutting the surefire plugin
memory reservation to that level? If not, I think it might be time to wave
goodbye to 32-bit... I don't think anyone is really running Hadoop on 32-bit.
Even ARM has gone 64-bit.
> Surefire needs to make sure the JVMs it fires up are 64-bit
> -----------------------------------------------------------
>
> 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
>
> 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)
