lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4462) Publishing flushed segments is single threaded and too costly
Date Wed, 10 Oct 2012 07:43:03 GMT


Simon Willnauer updated LUCENE-4462:

    Attachment: LUCENE-4462.patch

here is a new patch adding back the safety forcePurge. I will commit this to trunk and let
it bake in a bit before I backport. I will keep this issue open until it's ported.
> Publishing flushed segments is single threaded and too costly
> -------------------------------------------------------------
>                 Key: LUCENE-4462
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>    Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0
>            Reporter: Michael McCandless
>            Assignee: Simon Willnauer
>             Fix For: 4.1, 5.0
>         Attachments: LUCENE-4462.patch, LUCENE-4462.patch
> Spinoff from
> The new TestBagOfPostings failed the build because it timed out after 2 hours ... but
in digging I found that it was a starvation issue: the 4 threads were flushing segments much
faster than the 1 thread could publish them.
> I think this is because publishing segments (DocumentsWriter.publishFlushedSegment) is
actually rather costly (creates CFS file if necessary, writes .si, etc.).
> I committed a workaround for now, to prevent starvation (see svn diff -c 1394704,
but we really should address the root cause by moving these costly ops into flush() so that
publishing is a low cost operation.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message