Memory leak in fetcher (1.0) ?

Have a 300K URLs segement to fetch (no parsing) I see memory continuously growing up... looking like a memory leak. I have patch 769, 770 installed, and did not see any other patches related to memory leak. -- -MilleBii-

Re: Memory leak in fetcher (1.0) ?

Does it run out of memory? Is GC able to reclaim consumed heap space? Have a 300K URLs segement to fetch (no parsing) I see memory continuously growing up... looking like a memory leak. I have patch 769, 770 installed, and did not see any other patches related to memory leak.

Re: Memory leak in fetcher (1.0) ?

How many threads do you have running concurrently? Is there any log output to indicate any warnings or errors otherswise? On Sat, Jul 2, 2011 at 7:40 AM, Markus Jelsma markus.jel...@openindex.iowrote: Does it run out of memory? Is GC able to reclaim consumed heap space? Have a 300K URLs

Fwd: Re: Memory leak in fetcher (1.0) ?

---BeginMessage--- Here's a snippet from our wiki, these settings dump GC logs to a file which you can inspect. -verbose:gc enables verbose logging of the garbage collectors -XX:+PrintGCTimeStamps enables printing of timestamps in the garbage collector logs -XX:+PrintGCDetails

Fwd: Reminder: TAC Assistance to ApacheCon NA 2011 closes July 8th

Begin forwarded message: From: Gavin McDonald ga...@16degrees.com.au Date: July 2, 2011 5:16:14 PM PDT To: p...@apache.org p...@apache.org Subject: Reminder: TAC Assistance to ApacheCon NA 2011 closes July 8th - Hi All, Just a friendly (and final) reminder that applications

Nutch 1.3 CommandLineOptions updated to reflect new changes

Hi, Just finished the above, which you can find here [1] so please check out the pages if you are having trouble passing parameters to any commands. It would be great to mention if there are any mistakes or even better edit or add any missing information you think would make the documentation