No, this is on a test system that is still smallish, approx 100,000
records of dummy data with Wikipedia articles as content at the time
this occurred.

I wouldn't expect rebuilding the index to stall the entire JVM, that
seems excessive...

Stephen Duncan Jr
www.stephenduncanjr.com



On Wed, Sep 28, 2011 at 4:43 PM, Markus Jelsma
<markus.jel...@openindex.io> wrote:
> Is this a huge index? Keep in mind that most spellchecker implementations
> rebuild the index which can stall the entire process if there are millions of
> full text documents to process.
>
> There is a new implementation called DirectSolrSpellchecker that doens't so a
> complete rebuild but i haven't tried it yet but should work with the
> SuggesterComonent. It's still experimental though.
>
>> We have a separate Java process indexing to Solr using SolrJ.  We are
>> using Solr 3.4.0, and Jetty version 8.0.1.v20110908.  We experienced
>> Solr hanging today.  For a period of approximately 10 minutes, it did
>> not respond to queries.  Our indexer sends a query to build a
>> spellcheck index after committing once it's added all new documents
>> (because we have auto-commits that we don't want to trigger rebuilding
>> the spellcheck, we don't use buildOnCommit), and then sends a query to
>> build the suggest component index.  We see this from the Solr log
>> during the period it was hung (we attempted to send several queries
>> during this time, but they do not appear in the log, or appear after
>> waiting for several minutes):
>>
>> 2011-09-28 13:18:03,217 [qtp10884088-13] INFO
>> org.apache.solr.core.SolrCore - [report] webapp= path=/select
>> params={spellcheck=true&qt=dismax&wt=javabin&rows=0&spellcheck.build=true&v
>> ersion=2} hits=98772 status=0 QTime=173594
>> 2011-09-28 13:28:18,857 [qtp10884088-89] INFO
>> org.apache.solr.spelling.suggest.Suggester - build()
>> ...
>> 2011-09-28 13:29:02,873 [qtp10884088-89] INFO
>> org.apache.solr.core.SolrCore - [report] webapp= path=/suggest
>> params={spellcheck=true&qt=/suggest&wt=javabin&spellcheck.build=true&versio
>> n=2} status=0 QTime=44016
>>
>> In our indexer log, we see just after this (13:28:19,217) the call to
>> build our suggestion index (which comes right after building the
>> spellcheck index) times out and throws a NoHttpResponseException: The
>> server localhost failed to respond.
>>
>> Any ideas?  Anything else we should look at to help diagnose?
>> ---
>> Stephen Duncan Jr
>> www.stephenduncanjr.com
>

Reply via email to