lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Resolved] (SOLR-3621) Fix concurrency race around newIndexWriter
Date Fri, 26 Oct 2012 15:39:12 GMT


Mark Miller resolved SOLR-3621.

       Resolution: Fixed
    Fix Version/s: 5.0

Have no seen any reports of problems here in a while, and all this had hardened a fair amount
by now.
> Fix concurrency race around newIndexWriter 
> -------------------------------------------
>                 Key: SOLR-3621
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: update
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 4.1, 5.0
>         Attachments: SOLR--3621.patch
> When I did the first big refactor on update handler, I was trying to never close the
index writer - I had to give in on this goal due to the replication handler - it requires
rebooting the indexwriter. At the time, I settled for allowing a little race that didn't show
up as an issue in tests - this IW reboot was always a bit of a hack in the past anyhow.
> Now that the dust has settled, we should make this air tight though. I'd like to make
opening a new indexwriter a full class citizen rather than a hacky method only used minimally
for replication to reboot things. It should be a solid API that is valid for any uses down
the road.
> For some IW config changes, we may want to do it in 'some' cases on reload.
> To do this, we have to start ref counting iw use - so that we only actually open a new
one and close the old one when it's not in use at all.

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