lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5310) Merge Threads unnecessarily block on SerialMergeScheduler
Date Sun, 27 Apr 2014 15:38:15 GMT


Robert Muir commented on LUCENE-5310:

I also think CMS can deadlock (stall all merges) if you ever try to
decrease the maxMergeCount when too many merges were already running,
because the stall logic would get to a point where no thread would
ever be allowed to unstall. So I changed it (and MergeScheduler) to
require the maxMergeCount up front.

I proposed this on LUCENE-5310 a while back, but it didnt take then.

> Merge Threads unnecessarily block on SerialMergeScheduler
> ---------------------------------------------------------
>                 Key: LUCENE-5310
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>    Affects Versions: 4.5, 5.0
>            Reporter: Simon Willnauer
>            Priority: Minor
>             Fix For: 4.9, 5.0
>         Attachments: LUCENE-5310.patch, LUCENE-5310.patch, LUCENE-5310.patch, LUCENE-5310.patch,
LUCENE-5310.patch, LUCENE-5310.patch
> I have been working on a high level merge multiplexer that shares threads across different
IW instances and I came across the fact that SerialMergeScheduler actually blocks incoming
thread is a merge in going on. Yet this blocks threads unnecessarily since we pull the merges
in a loop anyway. We should use a tryLock operation instead of syncing the entire method?

This message was sent by Atlassian JIRA

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

View raw message