You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Joep Rottinghuis (JIRA)" <ji...@apache.org> on 2011/08/29 21:03:39 UTC

[jira] [Resolved] (MAPREDUCE-2906) FindBugs OutOfMemoryError

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joep Rottinghuis resolved MAPREDUCE-2906.
-----------------------------------------

    Resolution: Not A Problem

Even though same entry does not exist in hadoop-common build on 0.20-security, or hadoophdfs on 0.22, the mapreduce build actually already has a parameter for this: findbugs.heap.size

> FindBugs OutOfMemoryError
> -------------------------
>
>                 Key: MAPREDUCE-2906
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2906
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.22.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
>            Reporter: Joep Rottinghuis
>            Assignee: Joep Rottinghuis
>
> 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