r.java:4630)
>>> at
>>> org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:235)
>>> at
>>> org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:291)
>>>
>>> right? I can inte
erything is as planned".
>>
>> thanks
>>
>>
>> Vincent Sevel
>>
>>
>>
>>
>>
>>
>>
>>
>> Michael McCandless
>>
>>
>> 21.01.2011 15:48
>> Please respond to
>> java-user@l
;
>
> Vincent Sevel
>
>
>
>
>
>
>
>
> Michael McCandless
>
>
> 21.01.2011 15:48
> Please respond to
> java-user@lucene.apache.org
>
>
>
> To
> java-user@lucene.apache.org
> cc
>
> Subject
> Re: gracefully interrupting an opti
McCandless
21.01.2011 15:48
Please respond to
java-user@lucene.apache.org
To
java-user@lucene.apache.org
cc
Subject
Re: gracefully interrupting an optimize
No.
If you just do IW.close() <-- no boolean specified, then that defaults
to IW.close(true) which means "wait for all B
2011 15:48
Please respond to
java-user@lucene.apache.org
To
java-user@lucene.apache.org
cc
Subject
Re: gracefully interrupting an optimize
No.
If you just do IW.close() <-- no boolean specified, then that defaults
to IW.close(true) which means "wait for all BG merges to fini
No.
If you just do IW.close() <-- no boolean specified, then that defaults
to IW.close(true) which means "wait for all BG merges to finish".
So "normally" IW.close() reserves the right to take a long time.
But IW.close(false) should finish relatively quickly...
Mike
On Fri, Jan 21, 2011 at 9:2
Would that happen "automagically" at finalization?
paul
Le 21 janv. 2011 à 15:13, Michael McCandless a écrit :
> If you call optimize(false), that'll return immediately but run the
> optimize "in the background" (assuming you are using the default
> ConcurrentMergeScheduler).
>
> Later, when i
If you call optimize(false), that'll return immediately but run the
optimize "in the background" (assuming you are using the default
ConcurrentMergeScheduler).
Later, when it's time to stop optimizing, call IW.close(false), which
will abort any running merges yet keep any merges that had finished
Hi,
Each night I optimize an index that contains 35 millions docs. Its takes
about 1.5 hours. For maintenance reasons, it may happen that the machine
gets rebooted. In that case, server gets a chance to gracefully shutdown,
but eventually, the reboot script will kill the processes that did not
