What do you mean by it just crashes? Does the process stops execution? Does it takes too long to respond which might result in lots of 503s in your application? Does the system run out of resources?
Are you indexing and serving from the same server? It happened once with us that Solr was performing commit and then optimize while the load from app server was at its peak. This caused slow response from search server, which caused requests getting stacked up at app server and causing 503s. Could you look if you have a similar syndrome? *Pranav Prakash* "temet nosce" Twitter <http://twitter.com/pranavprakash> | Blog <http://blog.myblive.com> | Google <http://www.google.com/profiles/pranny> On Tue, Aug 2, 2011 at 15:31, alexander sulz <a.s...@digiconcept.net> wrote: > Hello folks, > > I'm using the latest stable Solr release -> 3.3 and I encounter strange > phenomena with it. > After about 19 hours it just crashes, but I can't find anything in the > logs, no exceptions, no warnings, > no suspicious info entries.. > > I have an index-job running from 6am to 8pm every 10 minutes. After each > job there is a commit. > An optimize-job is done twice a day at 12:15pm and 9:15pm. > > Does anyone have an idea what could possibly be wrong or where to look for > further debug info? > > regards and thank you > alex >
