Bill Graham wrote:
Then it seemed to run well for about an hour and I saw this:
Oct 28, 2008 10:38:51 PM org.apache.solr.update.DirectUpdateHandler2
commit
INFO: start commit(optimize=false,waitFlush=true,waitSearcher=true)
Oct 28, 2008 10:38:51 PM org.apache.solr.common.SolrException log
S
m on is pretty tight on memory.
thanks!
Bill
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Thursday, October 30, 2008 8:52:32 AM
Subject: Re: corrupt solr index on ec2
On Thu, Oct 30, 2008 at 2:06 AM, Bill Graham <[EMAIL PRO
One small correction below:
Yonik Seeley wrote:
- I've seen OOM exceptions during warming. I've changed
maxWarmingSearchers=1, which I suspect will do he trick
OOM errors are really tricky - if they happen in the wrong place, it's
hard to recover gracefully from. Correctly cleaning up after
On Thu, Oct 30, 2008 at 2:06 AM, Bill Graham <[EMAIL PROTECTED]> wrote:
> I've been running solr 1.3 on an ec2 instance for a couple of weeks and I've
> had some stability issues. It seems like I need to bounce the app once a day.
> That I could live with and ultimately maybe troubleshoot, but wh
Hi,
I've been running solr 1.3 on an ec2 instance for a couple of weeks and I've
had some stability issues. It seems like I need to bounce the app once a day.
That I could live with and ultimately maybe troubleshoot, but what's more
disturbing is that three times in the last 2 weeks my index ha
