On 6/13/2018 4:04 AM, Markus Jelsma wrote:
You mentioned shard handler tweaks, thanks. I see we have an incorrect setting
there for maximumPoolSize, way too high, but that doesn't account for the
number of threads created. After reducing the number, for dubious reasons,
twice the number of
production memory leak in a controlled test environment, let me know/
Thanks,
Markus
-Original message-
> From:Shawn Heisey
> Sent: Sunday 10th June 2018 22:42
> To: solr-user@lucene.apache.org
> Subject: Re: 7.3.1 creates thousands of threads after start up
>
> O
On 6/8/2018 8:59 AM, Markus Jelsma wrote:
> 2018-06-08 14:02:47.382 ERROR (qtp1458849419-1263) [ ] o.a.s.s.HttpSolrCall
> null:org.apache.solr.common.SolrException: Error trying to proxy request for
> url: http://idx2:8983/solr/
> search/admin/ping
> Caused by:
Hello Deepak,
Not in-between.
Thanks,
Markus
-Original message-
> From:Deepak Goel
> Sent: Friday 8th June 2018 17:14
> To: solr-user@lucene.apache.org
> Subject: Re: 7.3.1 creates thousands of threads after start up
>
> Do these machines have a firewall in-between?
tart those as often as i restart this collection,
> as i am STILL trying to REPRODUCE the dreaded memory leak i reported having
> on 7.3 about two weeks ago. Sorry, but i drives me nuts!
>
> Thanks,
> Markus
>
> -Original message-
> > From:Shawn Heisey
> > Sent:
solr-user@lucene.apache.org
> Subject: Re: 7.3.1 creates thousands of threads after start up
>
> On 6/8/2018 8:17 AM, Markus Jelsma wrote:
> > Our local test environment mini cluster goes nuts right after start up. It
> > is a two node/shard/replica collection starts up normally
On 6/8/2018 8:17 AM, Markus Jelsma wrote:
> Our local test environment mini cluster goes nuts right after start up. It is
> a two node/shard/replica collection starts up normally if only one node start
> up. But as soon as the second node attempts to join the cluster, both nodes
> go crazy,
Hello,
Our local test environment mini cluster goes nuts right after start up. It is a
two node/shard/replica collection starts up normally if only one node start up.
But as soon as the second node attempts to join the cluster, both nodes go
crazy, creating thousands of threads with identical
