I have seen a lot of CLOSE_WAIT in the past.
In many cases, it was that the client application was not releasing/closing
or pooling connections properly.
I would suggest you double check the client code first.
On 2 February 2018 at 23:52, mmb1234 <m...@vmware.com> wrote:
> > You said that you're running Solr 6.2.2, but there is no 6.2.2 version.
> > but the JVM argument list includes "-Xmx512m" which is a 512MB heap
> My typos. They're 6.6.2 and -Xmx30g respectively.
> > many open connections causes is a large number of open file handles,
> solr [ /opt/solr/server/logs ]$ sysctl -a | grep vm.max_map_count
> vm.max_map_count = 262144
> The only thing I notice right before solr shutdown messages in solr.log the
> /update QTime goes from ~500ms to ~250000.
> There is an automated health check that issues a kill on the <solrpid> due
> to http connection timeout.
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Menelic Ltd | Applied Knowledge Is Power
Office : +441444702101
Menelic Ltd: menelic.com
Visitor Management System: menelicvisitor.com