lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andi Vajda (JIRA)" <>
Subject [jira] Updated: (LUCENE-1339) Add IndexReader.acquire() and release() methods using IndexReader's ref counting
Date Fri, 18 Jul 2008 13:24:31 GMT


Andi Vajda updated LUCENE-1339:

    Attachment: lucene-1339.patch

> Add IndexReader.acquire() and release() methods using IndexReader's ref counting
> --------------------------------------------------------------------------------
>                 Key: LUCENE-1339
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>            Reporter: Andi Vajda
>             Fix For: 2.3.2
>         Attachments: lucene-1339.patch
> From:
> I have a server where a bunch of threads are handling search requests. I
> have a another process that updates the index used by the search server and
> that asks the searcher server to reopen its index reader after the updates
> completed.
> When I reopen() the index reader, I also close the old one (if the reopen()
> yielded a new instance). This causes problems for the other threads that
> are currently in the middle of a search request.
> I'd like to propose the addition of two methods, acquire() and release() 
> (attached to this bug report), that increment/decrement the ref count that IndexReader

> instances currently maintain for related purposes. That ref count prevents 
> the index reader from being actually closed until it reaches zero.
> My server's search threads, thus acquiring and releasing the index reader 
> can be sure that the index reader they're currently using is good until 
> they're done with the current request, ie, until they release() it.

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