Thanks all, I figured there would be more talk about daemontools if there were really a need. I appreciate the input and for starters we'll put two slaves behind a load balancer and grow it from there.
Lovin' Solr So Far! We were using alta vista as our search engine... it was sooo 90's! haha Thanks again, Robi -----Original Message----- From: Rafał Kuć [mailto:ra...@alud.com.pl] Sent: Monday, August 03, 2009 11:00 AM To: solr-user@lucene.apache.org Subject: Re: 99.9% uptime requirement Hello! Robert, from my experience with Solr (since 1.2 and running few 1.4 deployments) Solr does not need any kind of mechanism to ensure it will auto start on crash, because I didn`t see it crash on it`s own fault. Just ensure, You have not one instance of Solr, and run it behind a proxy or load balancer of some kind. -- Regards, Rafał Kuć > So then would the 'right' thing to do be to run it under something like > Daemontools so it bounces back up on a crash? Do any other people use > this approach or is there something better to make it come back up? > Speaking of overly large caches, if I have solr running on a machine > with 8GB main memory is it going to hurt to make some huge cache sizes? > Are these settings reasonable? With a small index I have been getting > some great hit-rates. > <ramBufferSizeMB>1024</ramBufferSizeMB> > <filterCache class="solr.FastLRUCache" size="350000" > initialSize="512" autowarmCount="80"/> > <queryResultCache class="solr.LRUCache" size="512000000" > initialSize="512" autowarmCount="80"/> > <documentCache class="solr.FastLRUCache" size="512000" > initialSize="512" autowarmCount="0"/> > Thanks > Robi > -----Original Message----- > From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com] > Sent: Friday, July 31, 2009 11:37 PM > To: solr-user@lucene.apache.org > Subject: Re: 99.9% uptime requirement > Robi, > Solr is indeed very stable. However, it can crash and I've seen it > crash. Or rather, I should say I've seen the JVM that runs Solr crash. > For instance, if you have a servlet container with a number of webapps, > one of which is Solr, and one of which has a memory leak, I believe all > webapps will suffer and "crash". And even if you have just Solr in your > servlet container, it can OOM, say if you specify overly large caches or > too frequent commits, etc. > Otis > -- > Sematext is hiring -- http://sematext.com/about/jobs.html?mls > Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR > ----- Original Message ---- >> From: Robert Petersen <rober...@buy.com> >> To: solr-user@lucene.apache.org >> Sent: Friday, July 31, 2009 12:18:55 PM >> Subject: 99.9% uptime requirement >> Hi all, >> My solr project powers almost all the pages in our site and so needs > to >> be up period. My question is what can I do to ensure that happens? >> Does solr ever crash, assuming reasonable load conditions and no > extreme >> index sizes? >> I saw some comments about running solr under daemontools in order to > get >> an auto-restart on crashes. From what I have seen so far in my > limited >> experience, solr is very stable and never crashes (so far). Does > anyone >> else have this requirement and if so how do they deal with it? Is >> anyone else running solr under daemontools in a production site? >> Thanks for any input you might have, >> Robi
