lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hans Lund <>
Subject NRT indexing and ControlledRealTimeReopenThread
Date Thu, 20 Feb 2014 09:37:44 GMT
Hi all

I'm a bit unsure about the intended function of
the ControlledRealTimeReopenThread in a NRT context - especially regarding
stale times.

As of now if you are waiting for a generation to become refreshed, it looks
like the stale time is either the min stale time or the max stale time. Is
this the intended behavior?

What i'm really looking for is 2 stale times with a slightly different
semantics. a stale time for refreshing when no specific generation is
needed, and another stale time for blocking acquiring of the blocked
searcher, (well the last time can actually be avoided all together as I
can't see any usage for a blocking acquiring should actually sleep at all
It would be better to run the SearchManager.maybeRefreshBlocking(); in the
thread needing the searcher @ a current generation.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message