Yonik: > If that's not the problem, you could decrease memory usage > due to faceting by upgrading to Solr 1.2 and using > facet.enum.cache.minDf
Is it hard to upgrade from 1.1 to 1.2? We were considering making that change if it wouldn't cost us a lot of downtime. can you help me understand what "using facet.enum.cache.minDf" means? Is that a setting in the config file? Dave W > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Yonik Seeley > Sent: Monday, July 30, 2007 3:29 PM > To: solr-user@lucene.apache.org > Subject: Re: Please help! Solr 1.1 HTTP server stops responding > > Grep for PERFORMANCE in the logs to make sure that you aren't > running into a scenario where more than one searcher is > warming in the background. > > If that's not the problem, you could decrease memory usage > due to faceting by upgrading to Solr 1.2 and using > facet.enum.cache.minDf > > -Yonik > > On 7/30/07, Kevin Holmes <[EMAIL PROTECTED]> wrote: > > Just got this: > > > > > > > > Jul 30, 2007 3:02:14 PM org.apache.solr.core.SolrException log > > SEVERE: java.lang.OutOfMemoryError: Java heap space > > > > Jul 30, 2007 3:02:30 PM org.apache.solr.core.SolrException log > > SEVERE: java.lang.OutOfMemoryError: Java heap space > > > > > > > > > > > > Kevin Holmes > > eNR Services, Inc. > > 20 Glover Ave. 2nd Floor > > Norwalk, CT. 06851 > > 203-849-7248 > > [EMAIL PROTECTED] > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Yonik > > Seeley > > Sent: Monday, July 30, 2007 2:55 PM > > To: solr-user@lucene.apache.org > > Subject: Re: Please help! Solr 1.1 HTTP server stops responding > > > > On 7/30/07, David Whalen <[EMAIL PROTECTED]> wrote: > > > We increased the heap size to 1500M and that didn't seem to help. > > > In fact, the crashes seem to occur more now than ever. We're > > > constantly restarting solr just to get a response. > > > > > > I don't know enough to know where the log files are to > answer your > > > question > > > > Me neither ;-) > > Solr's example app that uses Jetty just has logging going to stdout > > (the console) to make it clear and visible to new users > when an error > > happens. Hopefully you've configured Jetty to log to files, or at > > least redirected Jetty's stdout/stderr to a file. > > You need to look around and try and find those log files. > > If you find them, one thing to look for would be "WARNING" > in the log > > files. Another thing to look for would be "Exception" or "Memory" > > > > > So maybe it's actually Jetty that's messing me up? How > can I make > > > sure of that? > > > > Perhaps point your browser at http://localhost:8983/ and see if you > > get any reponse at all. > > > > -Yonik > > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.476 / Virus Database: 269.10.25/926 - Release > Date: 7/29/2007 11:14 PM > >
