[
https://issues.apache.org/jira/browse/LUCENE-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-4660:
---------------------------------------
Attachment: LUCENE-4660.patch
Simple patch: we were missing a notifyAll after a single merge thread pulls its
next merge.
> When ConcurrentMergeScheduler stalls incoming threads it has unexpected
> hysteresis
> ----------------------------------------------------------------------------------
>
> Key: LUCENE-4660
> URL: https://issues.apache.org/jira/browse/LUCENE-4660
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Attachments: LUCENE-4660.patch
>
>
> Eg if you set maxMergeCount to 2, as soon as a 3rd merge need to kick off, we
> stall incoming segment-creating threads. Then we wait ... and we are
> supposed to resume the threads when the merge count drops back to 2, but
> instead we are only resuming when merge count gets to 1. Ie, we stall for
> too long (= unexpected hysteresis).
--
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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
