[ https://issues.apache.org/jira/browse/NUTCH-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564114#comment-13564114 ]
Hudson commented on NUTCH-1284: ------------------------------- Integrated in Nutch-trunk #2103 (See [https://builds.apache.org/job/Nutch-trunk/2103/]) NUTCH-1284 Add site fetcher.max.crawl.delay as log output by default (Revision 1439289) Result = SUCCESS tejasp : http://svn.apache.org/viewvc/nutch/trunk/?view=rev&rev=1439289 Files : * /nutch/trunk/CHANGES.txt * /nutch/trunk/src/java/org/apache/nutch/fetcher/Fetcher.java > Add site fetcher.max.crawl.delay as log output by default. > ---------------------------------------------------------- > > Key: NUTCH-1284 > URL: https://issues.apache.org/jira/browse/NUTCH-1284 > Project: Nutch > Issue Type: New Feature > Components: fetcher > Affects Versions: nutchgora, 1.5 > Reporter: Lewis John McGibbney > Assignee: Tejas Patil > Priority: Trivial > Fix For: 1.7, 2.2 > > Attachments: NUTCH-1284-2.x.v1.patch, NUTCH-1284.patch, > NUTCH-1284-trunk.v1.patch > > > Currently, when manually scanning our log output we cannot infer which pages > are governed by a crawl delay between successive fetch attempts of any given > page within the site. The value should be made available as something like: > {code} > 2012-02-19 12:33:33,031 INFO fetcher.Fetcher - fetching > http://nutch.apache.org/ (crawl.delay=XXXms) > {code} > This way we can easily and quickly determine whether the fetcher is having to > use this functionality or not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira