You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Julien Nioche (JIRA)" <ji...@apache.org> on 2009/11/28 17:05:20 UTC

[jira] Commented: (NUTCH-770) Timebomb for Fetcher

    [ https://issues.apache.org/jira/browse/NUTCH-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783248#action_12783248 ] 

Julien Nioche commented on NUTCH-770:
-------------------------------------

The log simply shows that the patch has not been applied properly. 
See http://markmail.org/message/wbd3r3t5bfxzkbpn for a discussion on how to apply patches

Should work fine from the root directory of Nutch with 
patch -p0 < ~/Desktop/NUTCH-770.patch

> Timebomb for Fetcher
> --------------------
>
>                 Key: NUTCH-770
>                 URL: https://issues.apache.org/jira/browse/NUTCH-770
>             Project: Nutch
>          Issue Type: Improvement
>            Reporter: Julien Nioche
>         Attachments: log-770, NUTCH-770.patch
>
>
> This patch provides the Fetcher with a timebomb mechanism. By default the timebomb is not activated; it can be set using the parameter fetcher.timebomb.mins. The number of minutes is relative to the start of the Fetch job. When the number of minutes is reached, the QueueFeeder skips all remaining entries then all active queues are purged. This allows to keep the Fetch step under comtrol and works well in combination with NUTCH-769

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.