[ 
https://issues.apache.org/jira/browse/SOLR-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971259#comment-15971259
 ] 

Scott Blum commented on SOLR-10420:
-----------------------------------

[~caomanhdat] I didn't literally mean that we should bring back the isDirty 
bit.  I meant that clearly the last time around, there was a hole in the design 
that led to this leak.  I want to take the opportunity to re-look at the design 
again as a whole and make sure everything seems good, and we're not just 
putting a band-aid on it.  You may have already done this, so just give me a 
little bit to catch up. :D


> Solr 6.x leaking one SolrZkClient instance per second
> -----------------------------------------------------
>
>                 Key: SOLR-10420
>                 URL: https://issues.apache.org/jira/browse/SOLR-10420
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 5.5.2, 6.4.2, 6.5
>            Reporter: Markus Jelsma
>         Attachments: OverseerTest.106.stdout, OverseerTest.119.stdout, 
> OverseerTest.80.stdout, OverseerTest.DEBUG.43.stdout, 
> OverseerTest.DEBUG.48.stdout, OverseerTest.DEBUG.58.stdout, SOLR-10420.patch, 
> SOLR-10420.patch, SOLR-10420.patch, SOLR-10420.patch, SOLR-10420.patch
>
>
> One of our nodes became berzerk after a restart, Solr went completely nuts! 
> So i opened VisualVM to keep an eye on it and spotted a different problem 
> that occurs in all our Solr 6.4.2 and 6.5.0 nodes.
> It appears Solr is leaking one SolrZkClient instance per second via 
> DistributedQueue$ChildWatcher. That one per second is quite accurate for all 
> nodes, there are about the same amount of instances as there are seconds 
> since Solr started. I know VisualVM's instance count includes 
> objects-to-be-collected, the instance count does not drop after a forced 
> garbed collection round.
> It doesn't matter how many cores or collections the nodes carry or how heavy 
> traffic is.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to