Ok when this crawl is finished (only 10 hours to go) I will try with
less fetchers. Am I right about the number of fetchers being
fetcher.threads.fetch * number of map tasks running?
Andrzej Bialecki wrote:
Dennis Kubes wrote:
What is anybody else seeing for timeout percentages on large fetches?
We are running a 1M page crawl and seeing about a 10% timeout rate on
a 2Mbps line running about 165 fetchers I think. We have the
fetcher.threads.fetch set to 3 but have 55 map tasks as a default on
a 11 node cluster. If I am not mistaken this works out to 165
fetchers. It is running about 16 pages / second with about 10%
timeout and I didn't know if that would be due to my settings pretty
much pegging the available bandwidth or the websites I am crawling
being down or non-responsive. 10% seemed a little high to be downed
or non-responding sites.
I'm getting these symptoms when the total number of threads is too
high for available bandwidth.
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nutch-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-general
