[ https://issues.apache.org/jira/browse/NUTCH-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088661#comment-13088661 ]
Markus Jelsma commented on NUTCH-1067: -------------------------------------- Thanks for your comments. * modified the naming to use pages in conf and code as per your comment; * this is going to be difficuly because i measure the actual #pages/sec, that's always an integer, thoughts? * hasMore() method was added because i need to check outside the class if the feeder hasMore items, it was an internal to the method QueueFeeder.run(), i could make it a public attribute but choose a getter instead; > Configure minimum throughput for fetcher > ---------------------------------------- > > Key: NUTCH-1067 > URL: https://issues.apache.org/jira/browse/NUTCH-1067 > Project: Nutch > Issue Type: New Feature > Components: fetcher > Reporter: Markus Jelsma > Assignee: Julien Nioche > Priority: Minor > Fix For: 1.4, 2.0 > > Attachments: NUTCH-1067-1.4-1.patch, NUTCH-1067-1.4-2.patch, > NUTCH-1067-1.4-3.patch > > > Large fetches can contain a lot of url's for the same domain. These can be > very slow to crawl due to politeness from robots.txt, e.g. 10s per url. If > all other url's have been fetched, these queue's can stall the entire > fetcher, 60 url's can then take 10 minutes or even more. This can usually be > dealt with using the time bomb but the time bomb value is hard to determine. > This patch adds a fetcher.throughput.threshold setting meaning the minimum > number of pages per second before the fetcher gives up. It doesn't use the > global number of pages / running time but records the actual pages processed > in the previous second. This value is compared with the configured threshold. > Besides the check the fetcher's status is also updated with the actual number > of pages per second and bytes per second. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira