Re: Help with Solr 1.3 lockups?

2009-01-28 Thread Jerome L Quinn
Mark Miller markrmil...@gmail.com wrote on 01/26/2009 04:30:00 PM: Just a point or I missed: with such a large index (not doc size large, but content wise), I imagine a lot of your 16GB of RAM is being used by the system disk cache - which is good. Another reason you don't want to give too

Re: Help with Solr 1.3 lockups?

2009-01-28 Thread Mark Miller
org/apache/catalina/connector/Connector java/util/WeakHashMap $Entry399,913,269 bytes org/apache/catalina/connector/Connector java/lang/Object[ ] 197,256,078 bytes org/apache/lucene/search/ExtendedFieldCachejava/util/WeakHashMap$Entry [ ] 177,893,021 bytes

Re: Help with Solr 1.3 lockups?

2009-01-26 Thread Jerome L Quinn
Hi and thanks for looking at the problem ... Mark Miller markrmil...@gmail.com wrote on 01/15/2009 02:58:24 PM: Mark Miller markrmil...@gmail.com 01/15/2009 02:58 PM Re: Help with Solr 1.3 lockups? How much RAM are you giving the JVM? Thats running out of memory loading a FieldCache

Re: Help with Solr 1.3 lockups?

2009-01-26 Thread Jerome L Quinn
Lance Norskog goks...@gmail.com wrote on 01/20/2009 02:16:47 AM: Lance Norskog goks...@gmail.com 01/20/2009 02:16 AM Java 1.5 has thread-locking bugs. Switching to Java 1.6 may cure this problem. Thanks for taking time to look at the problem. Unfortunately, this is happening on Java 1.6,

Re: Help with Solr 1.3 lockups?

2009-01-26 Thread Mark Miller
setting if that makes sense. - Mark Jerome L Quinn wrote: Hi and thanks for looking at the problem ... Mark Miller markrmil...@gmail.com wrote on 01/15/2009 02:58:24 PM: Mark Miller markrmil...@gmail.com 01/15/2009 02:58 PM Re: Help with Solr 1.3 lockups? How much RAM are you giving

Re: Help with Solr 1.3 lockups?

2009-01-26 Thread Mark Miller
and thanks for looking at the problem ... Mark Miller markrmil...@gmail.com wrote on 01/15/2009 02:58:24 PM: Mark Miller markrmil...@gmail.com 01/15/2009 02:58 PM Re: Help with Solr 1.3 lockups? How much RAM are you giving the JVM? Thats running out of memory loading a FieldCache, which can

Re: Help with Solr 1.3 lockups?

2009-01-19 Thread Lance Norskog
Java 1.5 has thread-locking bugs. Switching to Java 1.6 may cure this problem. On Thu, Jan 15, 2009 at 10:57 AM, Jerome L Quinn jlqu...@us.ibm.com wrote: Hi, all. I'm running solr 1.3 inside Tomcat 6.0.18. I'm running a modified query parser, tokenizer, highlighter, and have a

Re: Help with Solr 1.3 lockups?

2009-01-16 Thread Bryan Talbot
I think it's pretty easy to check if SOLR is alive. Even from a shell script, a simple command like curl -iIs --url http://solrhost/solr/select?start=0rows=0; | grep -c HTTP/1.1 200 OK will return 1 if the response is an HTTP 200. If the return is not 1, then there is a problem. A

Help with Solr 1.3 lockups?

2009-01-15 Thread Jerome L Quinn
Hi, all. I'm running solr 1.3 inside Tomcat 6.0.18. I'm running a modified query parser, tokenizer, highlighter, and have a CustomScoreQuery for dates. After some amount of time, I see solr stop responding to update requests. When crawling through the logs, I see the following pattern: Jan

Re: Help with Solr 1.3 lockups?

2009-01-15 Thread Mark Miller
How much RAM are you giving the JVM? Thats running out of memory loading a FieldCache, which can be a more memory intensive data structure. It pretty much points to the JVM not having enough RAM to do what you want. How many fields do you sort on? How many fields do you facet on? How much RAM

Re: Help with Solr 1.3 lockups?

2009-01-15 Thread Stephen Weiss
I've been wondering about this one myself - most of the services we have installed work this way, if they crash out for whatever reason they restart automatically (Apache, MySQL, even the OS itself). Failures are detected and corrected by the load balancers and also in some cases by the