On Sat, Oct 4, 2008 at 11:55 AM, Uwe Klosa <[EMAIL PROTECTED]> wrote:
> A "Opening Server" is always happening directly after "start commit" with no
> delay.
Ah, so it doesn't look like it's the close of the IndexWriter then!
When do you see the "end_commit_flush"?
Could you post everything in your log between when the commit begins
and when it ends?
Is this a live server (is query traffic continuing to come in while
the commit is happening?) If so, it would be interesting to see (and
easier to debug) if it happened on a server with no query traffic.
> But I can see many {commit=} with QTime around 280.000 (4 and a half
> minutes)
> One difference I could see to your logging is that I have waitFlush=true.
> Could that have this impact?
These parameters (waitFlush/waitSearcher) won't affect how long it
takes to get the new searcher registered, but does affect at what
point control is returned to the caller (and hence when you see the
response). If waitSearcher==false, then you see the response before
searcher warming, otherwise it blocks until after. waitFlush==false
is not currently supported (it will always act as true), so your
change of that doesn't matter.
-Yonik
