[
https://issues.apache.org/jira/browse/NUTCH-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286545#comment-13286545
]
Markus Jelsma commented on NUTCH-1356:
--------------------------------------
Thanks for clearing things up.
These errors are indeed not reproducable. I collected about 12 of these error
throwing URL's and manually fetched them again with success, the parsechecker
also processes them without error.
The parser threads you refer to, is that a known problem? Can we solve it? Once
in a while a stalling parser eats up all remaining memory and dies.
> ParseUtil use ExecutorService instead of manually thread handling.
> ------------------------------------------------------------------
>
> Key: NUTCH-1356
> URL: https://issues.apache.org/jira/browse/NUTCH-1356
> Project: Nutch
> Issue Type: Improvement
> Reporter: Ferdy Galema
> Fix For: nutchgora, 1.6
>
> Attachments: NUTCH-1356-trunk-v2.patch, NUTCH-1356-trunk.patch,
> NUTCH-1356.patch
>
>
> Because ParseUtil manages it's own parser threads by creating a thread for
> every parse it sometimes happens that specific parsers are very expensive.
> For example, parsers that have threadlocal fields will initialize them for
> every item to be parsed.
> By simply introducing a caching ExecutorService the ParseUtil will be able to
> cache threads therefore parsing more efficient. See attached patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
