Re: Lucene coreClosedListeners memory issues

Thanks Adrien. I double checked on all the acquire, and it all correctly released in finally. What does SegmentCoreReaders.coreClosedListeners do? It seems to close caches. GC log indicates it is highly possible a leak issue as old gen is keeping increasing without dropping while CMS.

[Issue] omitNorms ignored in DefaultIndexingChain.getOrAddField method

Hello, I am a Lucene user and have been trying to write a search platform on top of lucene using version 6.6.1. I ran into some weird behavior and wanted to seek opinions from the community. I noticed that norms were being created even when I set *omitNorms=true* in the fieldTypes. I chased the is

Re: Lucene coreClosedListeners memory issues

And do you call release on every searcher that you acquire? On Mon, Jun 3, 2019 at 11:47 AM alex stark wrote: > > Hi Adrien, > > I didn't directly open readers. It is controlled by searcher manager. > > > > On Mon, 03 Jun 2019 16:32:06 +0800 Adrien Grand > wrote > > It looks like you

Re: Lucene coreClosedListeners memory issues

Hi Adrien, I didn't directly open readers. It is controlled by searcher manager. On Mon, 03 Jun 2019 16:32:06 +0800 Adrien Grand wrote It looks like you are leaking readers. On Mon, Jun 3, 2019 at 9:46 AM alex stark wrote: > > Hi e

Re: Lucene coreClosedListeners memory issues

It looks like you are leaking readers. On Mon, Jun 3, 2019 at 9:46 AM alex stark wrote: > > Hi experts, > > > > I recently have memory issues on Lucene. By checking heap dump, most of them > are occupied by SegmentCoreReaders.coreClosedListeners which is about nearly > half of all. > > > > > >

Lucene coreClosedListeners memory issues

Hi experts, I recently have memory issues on Lucene. By checking heap dump, most of them are occupied by SegmentCoreReaders.coreClosedListeners which is about nearly half of all. Dominator Tree num retain size(bytes) percent percent(live) class Name --