lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: LockFactory issue observed in lucene while getting instance of indexWriter
Date Fri, 01 Jul 2016 09:40:16 GMT
That looks like correct usage of MultiSearcher ... just be sure the
"release" happens in a finally clause.

But have a look at my prior email ... it's best to keep a single
IndexWriter open per index, and pass that writer when you create your
SearcherManagers.

Mike McCandless

Mike McCandless

http://blog.mikemccandless.com

On Wed, Jun 29, 2016 at 8:10 AM, Mukul Ranjan <mranjan@egain.com> wrote:

> Hi Mike,
>
>
>
> I observed the issue from some time and observed that there may issue with
> the MultiSearcher that I’m using for searcher over multiple index folders.
>
>
>
> I’m getting the searcher instance by using below code –  (Note: Searchable
> is the object of searchManager)
>
>
>
> IndexReader[] readers = new IndexReader[searchables.length];
>
> IndexSearcher[] tempSearchers = new IndexSearcher[searchables.length];
>
> for (int i = 0; i < searchables.length; i++)
>
> {
>
> tempSearchers[i] = searchables[i].getSearcher(callerContext);
>
> readers[i] = (tempSearchers[i]).getIndexReader();
>
> }
>
> MultiReader multiReader = new MultiReader(readers, false);
>
> IndexSearcher searcher = new IndexSearcher(multiReader);
>
>
>
> and releasing the searchManager using the below code-
>
>
>
> *for* (*int* i = 0; i < searchables.length; i++)
>
> *try*
>
> {
>
> searchables[i].releaseSearcher(tempSearchers[i]);
>
>       }
>
> *catch* (IOException e)
>
> {
>
> *mLogger*.logException(Level.*ERROR*, callerContext, *mSrcInfo*, "Falied
> to release searcher ", e);
>
> }
>
> }
>
>
>
> Do you think it’s right way to use MultiSearcher? If not, please suggest a
> way to use MultiSearcher.
>
>
>
> Thanks,
>
> Mukul Ranjan
>
>
>
> *From:* Michael McCandless [mailto:lucene@mikemccandless.com]
> *Sent:* Friday, June 17, 2016 3:28 PM
> *To:* Mukul Ranjan <mranjan@egain.com>
>
> *Subject:* Re: LockFactory issue observed in lucene while getting
> instance of indexWriter
>
>
>
> Why do you need to close and reopen the IndexWriter?  Can you leave it
> open indefinitely?
>
>
>
> Another option is to get a new Directory instance each time you want to
> open a new IndexWriter.
>
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
>
> On Fri, Jun 17, 2016 at 5:02 AM, Mukul Ranjan <mranjan@egain.com> wrote:
>
> No, We are not opening  any near-real-time readers, but still the issue
> coming.
>
>
>
> Thanks,
>
> Mukul
>
>
>
> *From:* Michael McCandless [mailto:lucene@mikemccandless.com]
> *Sent:* Friday, June 17, 2016 12:56 AM
> *To:* Mukul Ranjan <mranjan@egain.com>
> *Cc:* Lucene Users <java-user@lucene.apache.org>
>
> *Subject:* Re: LockFactory issue observed in lucene while getting
> instance of indexWriter
>
>
>
> But do you open any near-real-time readers from this writer?
>
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
>
> On Thu, Jun 16, 2016 at 1:01 PM, Mukul Ranjan <mranjan@egain.com> wrote:
>
> Hi Michael,
>
>
>
> Thanks for your reply.
>
> I’m running it on windows. I have checked my code, I’m closing IndexWriter
> after adding document to it.
>
> We are not getting this issue always but it’s frequency is high in our
> application. Can you please provide your suggestion?
>
>
>
> Thanks,
>
> Mukul
>
>
>
> *From:* Michael McCandless [mailto:lucene@mikemccandless.com]
> *Sent:* Thursday, June 16, 2016 10:22 PM
> *To:* Lucene Users <java-user@lucene.apache.org>; Mukul Ranjan <
> mranjan@egain.com>
> *Subject:* Re: LockFactory issue observed in lucene while getting
> instance of indexWriter
>
>
>
> Are you running on Windows?
>
>
>
> This is not a LockFactory issue ... it's likely caused because you closed
> IndexWriter, and then opened a new one, before closing NRT readers you had
> opened from the first writer?
>
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
>
> On Thu, Jun 16, 2016 at 6:19 AM, Mukul Ranjan <mranjan@egain.com> wrote:
>
> Hi,
>
> I'm observing below exception while getting instance of indexWriter-
>
> java.lang.IllegalArgumentException: Directory MMapDirectory@"directoryName"
> lockFactory=org.apache.lucene.store.NativeFSLockFactory@1ec79746 still
> has pending deleted files; cannot initialize IndexWriter
>
> Is it related to the default used NativeFSLockFactory. Should I use
> simpleFSLockFactory to avoid this type of issue. Please suggest as I'm
> getting the above exception in my application.
>
> Thanks,
> Mukul
> Visit eGain on YouTube<https://www.youtube.com/user/egainchannel> and
> LinkedIn<https://www.linkedin.com/company/egain-corporation>
>
>
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message