Re: Default LRUQueryCache causing OOO exception

2016-10-13 Thread Rahul Chandwani
suggestion. Here no searcher manager is used, we open new reader/searcher for every request. Same 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

Re: Default LRUQueryCache causing OOO exception

2016-10-12 Thread Rahul Chandwani
: 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

Re: Default LRUQueryCache causing OOO exception

2016-10-12 Thread Rahul Chandwani
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

Re: Default LRUQueryCache causing OOO exception

2016-10-12 Thread Rahul Chandwani
would be that you are dealing with lots of IndexReader instances in the same JVM. Are you able to count how many instance of CompressingStoredFieldReader were present in the heap? Le mer. 12 oct. 2016 à 09:08, Rahul Chandwani a écrit : > Hello, > > > We are using lucene 5.5.2 for se

Default LRUQueryCache causing OOO exception

2016-10-12 Thread Rahul Chandwani
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