lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer" <>
Subject Re: Spawn an indexing thread on every update
Date Fri, 12 Sep 2008 11:06:00 GMT
I guess similar problems have been discussed on the list over and over again.
Why don't you use a single update thread which takes care of batch
processing, commit threshold or performs commits after a certain time
This would at least prevent you from spawning all the threads which
is, as far as I can tell not necessary.
Your update thread could also notify you searcher to reopen the index
as soon as a change or a batch was commited.
If you are looking for examples you might find some good examples in
the Solr code.

- simon

On Fri, Sep 12, 2008 at 11:29 AM, Ian Lea <> wrote:
> Hi
> Why 15 mins?  Can you try lower values to get a balance between load
> and freshness?
> --
> Ian.
> On Thu, Sep 11, 2008 at 9:43 PM, nobody <> wrote:
>> Hi,
>>  In our application, I want users to be able to search for the updates they
>> make almost immediately. Hence, whenever they update, I spawn a thread
>> immediately to index. However, when the load on the application is very high
>> the number of threads spawned increases, and this results in "cannot create
>> native thread" error.
>> We are thinking of running the indexing thread once in every 15 mins,
>> through a scheduler, and buffer all the writes till the thread runs.
>> However, this will result in stale results on the search. Please advice what
>> is the best approach in this regard.
>> -thanks
>> --
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message