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 22:15:15 GMT


Michael McCandless commented on LUCENE-2618:

bq. Just want to point out that calling maybeMerge is as explicit as calling optimize.

But: apps don't normally call maybeMerge?  This is typically called within IW, eg on segment

I mean, it is public so apps can call it, but I expect very few do (vs optimize which apps
use alot).  It's the exception not the rule...

I guess I feel that close should try to close quickly -- an app would not expect close to
randomly take a long time (it's already bad enough since a large merge could be in process...).
  So, allowing other merges to start up, which could easily be large merges since they are
follow-on ones, would make that worse.

Alternatively, we could define the semantics of close as being allowed to prevent a running
optimize from actually completing?  Then we'd have to change this test, eg to call .waitForMerges
before close.

> 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