A couple of follow up questions:
- What type of garbage collector is in use?
- How often are you optimizing the index?
- In solrconfig.xml what is the setting for <mainIndex><ramBufferSizeMB>?
- Right before and after you see this pause, check the output of
http://<host>:<port>/solr/admin/system,
specifically the output of <jvm><memory> and send this to the list.
If possible definitely watch memory usage with something like JConsole, or
start the JVM with some of these params:
–XX:+PrintGCDetails
–XX:+PrintGCTimeStamps
-Jay
On Tue, Jan 19, 2010 at 5:16 PM, Steve Conover <scono...@gmail.com> wrote:
> I'll play with the GC settings and watch memory usage (I've done a
> little bit of this already), but I have a sense that this isn't the
> problem.
>
> I should also note that in order to create the really long pauses I
> need to post xml files full of documents that haven't been added in a
> long time / ever. Once a set of documents is posted to /update, if I
> re-post it solr behaves pretty well - and that's true even if I
> restart solr.
>
> On Tue, Jan 19, 2010 at 3:05 PM, Yonik Seeley
> <yo...@lucidimagination.com> wrote:
> > On Tue, Jan 19, 2010 at 5:57 PM, Steve Conover <scono...@gmail.com>
> wrote:
> >> I'm using latest solr 1.4 with java 1.6 on linux. I have a 3M
> >> document index that's 10+GB. We currently give solr 12GB of ram to
> >> play in and our machine has 32GB total.
> >>
> >> We're seeing a problem where solr blocks during commit - it won't
> >> server /select requests - in some cases for more than 15-30 seconds.
> >> We'd like to somehow configure things such that there's no
> >> interruption in /select service.
> >
> > A commit shouldn't cause searches to block.
> > Could this perhaps be a stop-the-word GC pause that coincides with the
> commit?
> >
> > -Yonik
> > http://www.lucidimagination.com
> >
>
