Hi Shalin, > You can expect as many connection evictor threads I have (whysoever (*)) 27 SolrClient instances instantiated but I see ~95 "Connection Evictor" threads ...
>It turns out that I made a mistake in the patch I committed in...which names >threads like pool-123-thread-1282. >So if you take a thread dump from Solr 6.6 Also I cannot prove, but I do not recall seeing many pool-xxx-thread-yyyy in my stack traces. In one I have at hand I see 2 "pool-x-thread-y"-threads 27 "ForkJoinPool.commonPool-worker-xx"-threads So I guess it is/was the ForkJoinPool.commonPool-worker's, but 27 is not >90 Thx - Clemens (*) I will follow Shawn's advices in this thread asap -----Ursprüngliche Nachricht----- Von: Shalin Shekhar Mangar <shalinman...@gmail.com> Gesendet: Dienstag, 23. Oktober 2018 10:30 An: solr-user@lucene.apache.org Betreff: Re: AW: AW: 6.6 -> 7.5 SolrJ, seeing many "Connection evictor"-Threads You can expect as many connection evictor threads as the number of http client instances. This is true for both Solr 6.6 and 7.x. I was intrigued as to why you were not seeing the same threads in both versions. It turns out that I made a mistake in the patch I committed in SOLR-9290 where instead of using Solr's DefaultSolrThreadFactory which names threads with a proper prefix, I used Java's DefaultThreadFactory which names threads like pool-123-thread-1282. So if you take a thread dump from Solr 6.6, you should be able to find threads named like these which are sleeping at a similar place in the stack.
