Thanks, I eventually found where the job trackers were in the :50030 web page of the cloudera thing, and I saw it said "10 threads" for each crawler in the little status update box where it was telling me how far along each crawl was. I have to say, this whole thing (nutch/hadoop) is pretty flipping awesome. Great work.
I'm running on aws EC2 us-east and spidering sites that should be hosted on the CENIC network in California, do you have any suggestions on what a good number of threads to try per crawler might be in that situation (I'm guessing it might be hard to saturate the bandwidth)? I'm thinking I'll bump it up to at least 25. Thanks again, -- Brian |-----Original Message----- |From: Andrzej Bialecki [mailto:[email protected]] |Sent: Thursday, July 23, 2009 1:01 AM |To: [email protected] |Subject: Re: nutch -threads in hadoop | |Brian Tingle wrote: |> Hey, |> |> |> |> I'm playing around the nutch on hadoop; when I go |> |> hadoop jar nutch-1.0.job org.apache.nutch.crawl.Crawl -threads ... is |> that threads per node or total threads for all nodes? | |Threads per map task - if you run multiple map tasks per node then you |will get numThreads * numMapTasks per node. | |So be careful to set it to a number that doesn't overwhelm your network ;) | |-- |Best regards, |Andrzej Bialecki <>< | ___. ___ ___ ___ _ _ __________________________________ |[__ || __|__/|__||\/| Information Retrieval, Semantic Web |___|||__|| \| || | Embedded Unix, System Integration |http://www.sigram.com Contact: info at sigram dot com
