Re: Best way to prevent this search lockup (apparently caused during big segment merges)?

2010-04-26 Thread Chris Harris
o: solr-user@lucene.apache.org >> Sent: Thu, April 22, 2010 6:28:29 PM >> Subject: Best way to prevent this search lockup (apparently caused during >> big  segment merges)? >> >> I'm running Solr 1.4+ under Tomcat 6, with indexing and searching > requests >

Re: Best way to prevent this search lockup (apparently caused during big segment merges)?

2010-04-23 Thread Otis Gospodnetic
che.org > Sent: Thu, April 22, 2010 6:28:29 PM > Subject: Best way to prevent this search lockup (apparently caused during big > segment merges)? > > I'm running Solr 1.4+ under Tomcat 6, with indexing and searching requests > simultaneously hitting the same Solr machine

Re: Best way to prevent this search lockup (apparently caused during big segment merges)?

2010-04-23 Thread Michael McCandless
I don't know much about how Solr does its locking, so I'm guessing below: It looks like one thread is doing a commit, by closing the writer, and is likely holding a lock that prevents other (add/delete) ops from running? Probably this lock is held because the writer is in the process of being clos

Best way to prevent this search lockup (apparently caused during big segment merges)?

2010-04-22 Thread Chris Harris
I'm running Solr 1.4+ under Tomcat 6, with indexing and searching requests simultaneously hitting the same Solr machine. Sometimes Solr, Tomcat, and my (C#) indexing process conspire to render search inoperable. So far I've only noticed this while big segment merges (i.e. merges that take multiple