lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <>
Subject [jira] [Updated] (SOLR-10420) Solr 6.x leaking one SolrZkClient instance per second
Date Tue, 18 Apr 2017 18:33:42 GMT


Scott Blum updated SOLR-10420:
    Fix Version/s: master (7.0)

> Solr 6.x leaking one SolrZkClient instance per second
> -----------------------------------------------------
>                 Key: SOLR-10420
>                 URL:
>             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
>            Assignee: Scott Blum
>             Fix For: 5.5.5, 6.4.3, 6.5.1, master (7.0)
>         Attachments: OverseerTest.106.stdout, OverseerTest.119.stdout, OverseerTest.80.stdout,
OverseerTest.DEBUG.43.stdout, OverseerTest.DEBUG.48.stdout, OverseerTest.DEBUG.58.stdout,
SOLR-10420-dragonsinth.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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message