lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-2618) Intermittent failure in 3.x's backwards TestThreadedOptimize
Date Thu, 21 Oct 2010 12:52:15 GMT


Michael McCandless commented on LUCENE-2618:

If close(false) is called after optimize() was called, it means the app would like to abort
merges ASAP. If so, why would we consult the MP if we're instructed to abort?

Are you talking about a different use case?

Sorry, different use case.

This use case is you call .optimize(doWait=false) then you call a normal .close() (ie, wait
for merges).  In this case we wait for all running merges to finish, but don't start any new
ones.  My patch would still allow new ones to start if the merges are due to a running optimize.

Your use case, where .close(false) is called, will in fact abort all running merges and close
quickly.  Ie we will not start new merges, even for optimize, if you pass false to close,
with this pattch.

> Intermittent failure in 3.x's backwards TestThreadedOptimize
> ------------------------------------------------------------
>                 Key: LUCENE-2618
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>            Reporter: Michael McCandless
>             Fix For: 3.1, 4.0
>         Attachments: LUCENE-2618.patch
> Failure looks like this:
> {noformat}
>     [junit] Testsuite: org.apache.lucene.index.TestThreadedOptimize
>     [junit] Testcase: testThreadedOptimize(org.apache.lucene.index.TestThreadedOptimize):
>     [junit] null
>     [junit] junit.framework.AssertionFailedError: null
>     [junit] 	at org.apache.lucene.index.TestThreadedOptimize.runTest(
>     [junit] 	at org.apache.lucene.index.TestThreadedOptimize.testThreadedOptimize(
>     [junit] 	at org.apache.lucene.util.LuceneTestCase.runBare(
> {noformat}
> I just committed some verbosity so next time it strikes we'll have more details.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message