The memory usage is probably MMapDirectory, see: http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html, that's not a problem I'd guess.
The open file handles... and ones being open many times. 1> how many _total_ segment files do you have in all the replicas in the JVM? A single segment consists of 0_.fdt, 0_.fdx, 0_.tim etc..., the next segment _1.fdt, _1.fdx... So the total number of files will be much greater than the number of segments. If this total is in the 100K range, it's kind of normal, maybe. Or something. 2> Do you have any custom code? It's very easy to open a searcher and _not_ close it in custom code, which will keep file handles open. 3> Are you using CDCR? And if so, are you buffering? That might keep tlog files open. 4> If you shut down the JVM and restart Solr, do the index files (segment files and/or TLOGs) disappear? Not sure you can run this experiment on your system if it's prod, but it'd be some information to go on, indicating "something" is not closing searchers or the like. I'm not asking about file handles here, but rather do the files disappear off disk? Best, Erick On Tue, Sep 11, 2018 at 10:11 AM Boris Pasko <bpa...@exiger.com> wrote: > > > > Same picture on Solr 6.6.2, tested on various Oracle JVMs ranging > > from 1.8.0_171 to 1.8.0_171 > > From 1.8.0_171 to 1.8.0_181 > > > ––––––––––––––––––––––––––––––––––––– > The information contained in this message and any attachments may be > confidential and/or restricted and protected from disclosure. If the reader > of this message is not the intended recipient, disclosure, copying, use, or > distribution of the information included in this message is prohibited - > please destroy all electronic and paper copies and notify the sender > immediately.
