Hello Brad, At one point you said CPU is at 100% and there is no disk IO. Then in a separate email I think you said this happens during RAM -> Disk flush. Isn't there a contradiction here?
A few thread dumps may tell you where things are "stuck". Also, how does your JVM look while this is happening? Could this be just Garbage Collection? SPM (see URL in sig) may be helpful here. Otis ---- Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm ----- Original Message ----- > From: "Voth, Brad (GE Corporate)" <brad.v...@ge.com> > To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> > Cc: > Sent: Wednesday, August 29, 2012 1:05 PM > Subject: RE: Injest pauses > > Interestingly it is not pausing during every commit so at least a portion of > the > time the async commit code is working. Trying to track down the case where a > wait would still be issued. > > -----Original Message----- > From: Voth, Brad (GE Corporate) > Sent: Wednesday, August 29, 2012 12:32 PM > To: solr-user@lucene.apache.org > Subject: RE: Injest pauses > > Thanks, I'll continue with my testing and tracking down the block. > > -----Original Message----- > From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik Seeley > Sent: Wednesday, August 29, 2012 12:28 PM > To: solr-user@lucene.apache.org > Subject: Re: Injest pauses > > On Wed, Aug 29, 2012 at 11:58 AM, Voth, Brad (GE Corporate) > <brad.v...@ge.com> wrote: >> Anyone know the actual status of SOLR-2565, it looks to be marked as >> resolved in 4.* but I am still seeing long pauses during commits using >> 4.* > > SOLR-2565 is definitely committed - adds are no longer blocked by commits (at > least at the Solr level). > > -Yonik > http://lucidworks.com >
