This looks like the namenode has lost connection to one of the
datanodes. The default number of replications in ndfs is 3 and it
seems like the namenode has only 2 in its list so it logs this
warning. As Stefan suggested, you should check the diskspace on your
machines. If I recall correctly datanodes crash when they run out of
diskspace.
This could also explain your problem with the fetching. One datanode
runs out of diskspace and crashes while one of the tasktrackers is
writing data to it. You should also check if the partition with /tmp
has enough free space.
Yes, that also can happen.
Especially if, like us, you accidentally configure Nutch to use a
directory on the root volume, but your servers have been configured
with a separate filesystem for /data, and that's where all the disk
capacity is located.
-- Ken
Stefan Groschupf schrieb:
may the hdds are full?
try:
bin/nutch ndfs -report
Nutch generates some temporarily data until processing.
Am 30.01.2006 um 00:54 schrieb Mike Smith:
I forgot to mention the namenode log file gives me thousands of these:
060129 155553 Zero targets found,
forbidden1.size=2allowSameHostTargets=false
forbidden2.size()=0
060129 155553 Zero targets found,
forbidden1.size=2allowSameHostTargets=false
forbidden2.size()=0
--
Ken Krugler
Krugle, Inc.
+1 530-470-9200
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Nutch-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-general
