[
https://issues.apache.org/jira/browse/NUTCH-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882160#comment-17882160
]
Hudson commented on NUTCH-3058:
-------------------------------
FAILURE: Integrated in Jenkins build Nutch ยป Nutch-trunk #167 (See
[https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/167/])
NUTCH-3058 Fetcher: counter for hung threads (#820) (github:
[https://github.com/apache/nutch/commit/582cdd417b8ead6183db8cd6e787f612dbcd9f90])
* (edit) src/java/org/apache/nutch/fetcher/Fetcher.java
* (edit) conf/nutch-default.xml
> Fetcher: counter for hung threads
> ---------------------------------
>
> Key: NUTCH-3058
> URL: https://issues.apache.org/jira/browse/NUTCH-3058
> Project: Nutch
> Issue Type: Improvement
> Components: fetcher
> Affects Versions: 1.20
> Reporter: Sebastian Nagel
> Assignee: Sebastian Nagel
> Priority: Major
> Fix For: 1.21
>
>
> The Fetcher class defines a "hard" timeout defined as 50% of the MapReduce
> task timeout, see {{mapreduce.task.timeout}} and
> {{fetcher.threads.timeout.divisor}}. If there are fetcher threads running but
> without any progress during the timeout period (in terms of newly started
> fetch items), Fetcher is shut down to avoid that the task timeout is reached
> and the fetcher job is failed. The "hung threads" are logged together with
> the URL being fetched and (DEBUG level) the Java stack.
> In addition to logging, a job counter should indicate the number of hung
> threads. This would allow to see on the job level whether there are issues
> with hung threads. To trace the issues it's still required to look into the
> Hadoop task logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
