Re: Memory Issue with SnapPuller

2016-10-20 Thread Jihwan Kim
This is also the screenshot of jvisualvm. This exception occurred at 2:55PM and 3:40PM and OOME occurs at 3:41PM. SnapPuller - java.lang.InterruptedException at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:404) at java.util.concurrent.FutureTask.get(FutureTask.java:191) at SnapPul

Re: Memory Issue with SnapPuller

2016-10-20 Thread Jihwan Kim
Good points. I am able to create this with periodic snap puller and only one http request. When I load the Solr on tomcat, the initial memory usage was between 600M to 800 M. First time, I used 1.5 G and then increased the heap to 3.5G. (When I said 'triple', I meant comparing to the initial mem

Re: Memory Issue with SnapPuller

2016-10-20 Thread Erick Erickson
You say you tripled the memory. Up to what? Tripling from 500M t0 1.5G isn't likely enough, tripling from 6G to 18G is something else again You can take a look through any of the memory profilers and try to catch the objects (and where they're being allocated). The second is to look at the sta

Re: Memory Issue with SnapPuller

2016-10-20 Thread Jihwan Kim
Thank you Shawn. I understand the two options. After my own testing with a smaller heap, I increased my heap size more than triple, but OOME happens again with my testing cases under the controlled thread process. Increased heap size just delayed the OOME. Can you provide a feedback on my second q

Re: Memory Issue with SnapPuller

2016-10-20 Thread Shawn Heisey
On 10/20/2016 8:44 AM, Jihwan Kim wrote: > We are using Solr 4.10.4 and experiencing out of memory exception. It > seems the problem is cause by the following code & scenario. When you get an OutOfMemoryError exception that tells you there's not enough heap space, the place where the exception ha

Re: Memory Issue with SnapPuller

2016-10-20 Thread Jihwan Kim
A little more about "At certain timing, this method also throw " SnapPuller - java.lang.InterruptedException at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:404) at java.util.concurrent.FutureTask.get(FutureTask.java:191) at SnapPuller.openNewSearcherAndUpdateCommitPoint(SnapPulle

Re: Memory Issue with SnapPuller

2016-10-20 Thread Jihwan Kim
Sorry, wrong button was clicked. A little more about "At certain timing, this method also throw " SnapPuller - java.lang.InterruptedException at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:404) at java.util.concurrent.FutureTask.get(FutureTask.java:191) at SnapPuller.openNewSear