Shawn, Yes earlier I did not find out about the multiple searchers. I reached to this after debugging a lot. And now i can confirm it was the same searcher when i posted the question first time.
I reloaded the collection 15 minutes ago and now the stuck searcher is gone. So i won’t be able to tell you the warmup time for stuck searcher. But after reloading now the mapped total capacity has reached to 75 GB. On other servers it is still 25 GB. We do use our custom phonetic implementation. But it is running since years. On Fri, 7 Oct 2022 at 7:39 PM, Shawn Heisey <[email protected]> wrote: > On 10/7/22 07:55, Satya Nand wrote: > > I guess it is something related to mmap directory implementation of index > > directory though I could be wrong. > > That makes sense. MMAP space is not a count of memory actually taken, > just the amount of data that is accessible. The OS manages how much of > that data is actually in memory. > > > These 2 searchers are there since 11 am. And after every commit two more > > searchers are being opened again. > > I don't know what timezone you are in, but I am assuming that was quite > a while ago. Are you sure it's the exact same searcher that you saw at > 11 AM? What is the warmupTime for each searcher you see in Plugins/Stats? > > Just saw your additional message. Are you running with any modules or > custom code? Something that required loading extra jars? > > Thanks, > Shawn > >
