ame were not closed after use.
>
>
> Issue is resolved now.
>
>
> Thanks
>
> Rahul
>
>
> From: Michael McCandless
> Sent: Thursday, October 13, 2016 2:38:46 PM
> To: Lucene Users
> Cc: Rahul Chandwani
> Subject: Re: Defa
Subject: Re: Default LRUQueryCache causing OOO exception
These sounds like good ideas Trejkaz ... maybe open an issue and make
a starting patch so we can iterate?
I agree a try-w-resources solution, and/or a lambda solution, could be better.
Did you already share how you got it working for
These sounds like good ideas Trejkaz ... maybe open an issue and make
a starting patch so we can iterate?
I agree a try-w-resources solution, and/or a lambda solution, could be better.
Did you already share how you got it working for multiple indices?
Mike McCandless
http://blog.mikemccandless.
On Thu, Oct 13, 2016 at 6:32 AM, Michael McCandless
wrote:
> You must be calling SearcherManager.maybeRefresh periodically, which
> does open new NRT readers.
>
> Can you please triple check that you do in fact always release() after
> an acquire(), in a finally clause?
For what it's worth, I fou
sing NoMergePolicy. Default merge policy is used.
>
>
> Thanks
>
> Rahul
>
>
> From: Adrien Grand
> Sent: Wednesday, October 12, 2016 8:22:01 PM
> To: Rahul Chandwani; java-user@lucene.apache.org
> Subject: Re: Default LRUQueryCache c
: Wednesday, October 12, 2016 8:22:01 PM
To: Rahul Chandwani; java-user@lucene.apache.org
Subject: Re: Default LRUQueryCache causing OOO exception
After readers are released, are they also free to be garbage collected or
is something holding references to them?
How many indices do you have? Are you
) call is followed by release() call.
>
> --
> *From:* Adrien Grand
> *Sent:* Wednesday, October 12, 2016 7:55:58 PM
> *To:* Rahul Chandwani; java-user@lucene.apache.org
>
> *Subject:* Re: Default LRUQueryCache causing OOO exception
> Hi Rahul,
>
>
Hi Adrien,
Every acquire() call is followed by release() call.
From: Adrien Grand
Sent: Wednesday, October 12, 2016 7:55:58 PM
To: Rahul Chandwani; java-user@lucene.apache.org
Subject: Re: Default LRUQueryCache causing OOO exception
Hi Rahul,
The most likely
Sent: Wednesday, October 12, 2016 12:51 PM
> To: java-user@lucene.apache.org
> Subject: Re: Default LRUQueryCache causing OOO exception
>
>
> Hi Rahul,
>
> High memory from both these classes is unexpected. I am wondering that
> maybe your application does not clos
, 2016 12:51 PM
To: java-user@lucene.apache.org
Subject: Re: Default LRUQueryCache causing OOO exception
Hi Rahul,
High memory from both these classes is unexpected. I am wondering that maybe
your application does not close index readers when it doesn't need them
anymore? Another possibility
Hi Rahul,
High memory from both these classes is unexpected. I am wondering that
maybe your application does not close index readers when it doesn't need
them anymore? Another possibility would be that you are dealing with lots
of IndexReader instances in the same JVM. Are you able to count how ma
Hello,
We are using lucene 5.5.2 for search .
We are getting out of memory exception as default LRUQueryCache is occupying
more much more than default 32 MB memory.
Searcher Manager is used here to get an instance of index searcher to perform
search. Default lru query cache and default query
12 matches
Mail list logo
