You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2014/04/04 15:13:15 UTC
[jira] [Commented] (NUTCH-1746) OutOfMemoryError in Mappers
[ https://issues.apache.org/jira/browse/NUTCH-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959929#comment-13959929 ]
Lewis John McGibbney commented on NUTCH-1746:
---------------------------------------------
I am keen to learn of the volume of input(s) to the Mappers to result in OOM. Do you run with any specific values for _mapred.child.java.opts_ property (or similar)?
> OutOfMemoryError in Mappers
> ---------------------------
>
> Key: NUTCH-1746
> URL: https://issues.apache.org/jira/browse/NUTCH-1746
> Project: Nutch
> Issue Type: Bug
> Components: generator, injector
> Affects Versions: 1.7
> Environment: Nutch running in local mode with 4M+ domains in domain-urlfilter.txt
> Reporter: Greg Padiasek
> Attachments: Generator.patch, Injector.patch
>
>
> Initially I found that Generator was throwing OutOfMemoryError exception no matter how much RAM I allocated to JVM. I fixed the problem by moving URLFilters, URLNormalizers and ScoringFilters to top-level class as singletons and re-using them in all Generator mapper instances.
> Then I found the same problem in Injector and applied analogical fix.
> Now it seems that this issue may be common in all Nutch Mapper implementations.
> I was wondering if it would it be possible to integrate this kind of change
> in the upstream code base and potentially update all vulnerable Mapper classes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)