Hi Yonik. > What version of Solr are you running?
We're running: Solr Specification Version: 1.2.2007.08.24.08.06.00 Solr Implementation Version: nightly ${svnversion} - yonik - 2007-08-24 08:06:00 Lucene Specification Version: 2.2.0 Lucene Implementation Version: 2.2.0 548010 - buschmi - 2007-06-16 23:15:56 > Is the CPU pegged at 100% when it's unresponsive? It's a little difficult to be sure. We have a HT box and the CPU % we get back is misleading. I think it's safe to say we may spike up to 100% but we don't necessarily stay pegged there. > Have you taken a thread dump to see what is going on? We can't do it b/c during the unresponsive time we can't access the admin site (/solr/admin) at all. I don't know how to do a thread dump via the command line.... > Do you get into a situation where more than one searcher is > warming at a time? (there is configuration that can prevent > this one from happening). Forgive me when I say I'm not totally clear on what this question means. The index is constantly getting hit with a myriad or queries, if that's what you meant.... Thanks, Dave > -----Original Message----- > From: Yonik Seeley [mailto:[EMAIL PROTECTED] > Sent: Monday, October 08, 2007 2:23 PM > To: solr-user@lucene.apache.org > Subject: Re: Availability Issues > > On 10/8/07, David Whalen <[EMAIL PROTECTED]> wrote: > > We're running SOLR 1.2 with a 2.5G heap size. On any given > day, the > > system becomes completely unresponsive. > > We can't even get /solr/admin/ to come up, much less any select > > queries. > > What version of Solr are you running? > The first step to diagnose something like this is to figure > out what is going on... > Is the CPU pegged at 100% when it's unresponsive? > Have you taken a thread dump to see what is going on? > Do you get into a situation where more than one searcher is > warming at a time? (there is configuration that can prevent > this one from happening). > > -Yonik > >