[
https://issues.apache.org/jira/browse/HADOOP-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095362#comment-13095362
]
Joep Rottinghuis commented on HADOOP-7381:
------------------------------------------
HADOOP-7381 is not really needed for 0.22,
It was applicable to 0.20-security which is before the project split with a
large combined hadoop-common project.
After the split, hadoop-common is small enough that it does not run OOM with
the defaults.
This does not apply to Mavenization on trunk (at least not in the ant form).
I'll have to see if the same exists with Mavenization, but with a different
build, the error will be different if it exists at all.
> FindBugs OutOfMemoryError
> -------------------------
>
> Key: HADOOP-7381
> URL: https://issues.apache.org/jira/browse/HADOOP-7381
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 0.20.205.0
> Environment: FindBugs 1.3.9, ant 1.8.2, RHEL6, Jenkins 1.414 in
> Tomcat 7.0.14, Sun Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed
> mode)
> Reporter: Joep Rottinghuis
> Assignee: Joep Rottinghuis
> Priority: Minor
> Attachments: hadoop-7381.patch
>
>
> When running the findbugs target from Jenkins, I get an OutOfMemory error.
> The "effort" in FindBugs is set to Max which ends up using a lot of memory to
> go through all the classes. The jvmargs passed to FindBugs is hardcoded to
> 512 MB max.
> We can leave the default to 512M, as long as we pass this as an ant parameter
> which can be overwritten in individual cases through -D, or in the
> build.properties file (either basedir, or user's home directory).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
