--- Begin Message ---
2Gb is too much for the fetcher unless you're using a huge amount of threads.
You can easily answer the questions using a tool as JConsole. It, a.o.,
displays realtime graphs of JVM heap generations. A memory leak has a very
distinct appearance; a saw-tooth that never drops to a baseline and keeps
increasing until OOM is reached.
As long you don't run OOM there is no problem. I would advice to drop Xmx to
500MB orso as the more heap you have, the more work the GC has cleaning the
mess.
> Well I don't really know... on the last run the server hang and a hard
> reboot was required.
> Nothing noticeable in the logs.
>
> I have heap space set to -Xmx 2000, which I can increase but it ain't
> solving the memory leak.
>
>
>
> 2011/7/2 Markus Jelsma <[email protected]>
>
> > 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.
--- End Message ---
