nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Denny (JIRA)" <>
Subject [jira] Commented: (NUTCH-719) fetchQueues.totalSize incorrect in Fetcher2
Date Mon, 13 Jul 2009 08:31:14 GMT


Steven Denny commented on NUTCH-719:

perhaps i spoke too soon

10 threads, 15520 pages, 723 errors, 3.7 pages/s, 2972 kb/s, 
-activeThreads=10, spinWaiting=10, fetchQueues.totalSize=0, fetchQueues.count=0
Aborting with 10 hung threads.
Unable to resolve:, skipping.
Exception in thread "QueueFeeder" java.lang.NullPointerException
	at org.apache.hadoop.fs.BufferedFSInputStream.getPos(
	at org.apache.hadoop.fs.FSDataInputStream.getPos(
	at org.apache.hadoop.fs.ChecksumFileSystem$ChecksumFSInputChecker.readChunk(
	at org.apache.hadoop.fs.FSInputChecker.readChecksumChunk(
	at org.apache.hadoop.fs.FSInputChecker.fill(
	at org.apache.hadoop.mapred.MapTask$TrackedRecordReader.moveToNext(
	at org.apache.hadoop.mapred.MapTask$
	at org.apache.nutch.fetcher.Fetcher$

It apears that the feeder hung, but I'm not sure whether the exception raised is the cause
or the effect (i suspect it's the effect of the thread aborting)

I'm also not sure if any of these issues are vm related. Hopefully our real hardware will
turn up soon....

> fetchQueues.totalSize incorrect in Fetcher2
> -------------------------------------------
>                 Key: NUTCH-719
>                 URL:
>             Project: Nutch
>          Issue Type: Bug
>          Components: fetcher
>    Affects Versions: 1.0.0
>            Reporter: Julien Nioche
> I had a look at the logs generated by Fetcher2 and found cases where there were no active
fetchQueues but fetchQueues.totalSize was != 0
> fetcher.Fetcher2 - -activeThreads=200, spinWaiting=200, fetchQueues.totalSize=1, fetchQueues=0
> since the code relies on fetchQueues.totalSize to determine whether the work is finished
or not the task is blocked until the abortion mechanism kicks in
> 2009-03-12 09:27:38,977 WARN  fetcher.Fetcher2 - Aborting with 200 hung threads.
> could that be a synchronisation issue? any ideas?

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

View raw message