[
https://issues.apache.org/jira/browse/SOLR-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499123#comment-17499123
]
Mike Drob commented on SOLR-16046:
----------------------------------
So what it looks like is:
* Thread 79 is blocked on entering {{synchronized close()}} because Thread 81
is already there.
* Thread 81 is inside of close() and has sent a closeSession packet to the
server. It is waiting on the response (which will come on the eventQueue)
* Thread 83 is... waiting to read events off of the event queue?
So if there was an event coming then we would expect this all to drain
eventually. It's possible that amid all of the session expirations.
Possibly relevant, [[email protected]] added additional filters in
SOLR-15660 for "zkConnectionManagerCallback" threads in timed wait, these are
in untimed wait so it's not the same thing but possibly similar motivation.
> Thread leak in TestLeaderElectionZkExpiry
> -----------------------------------------
>
> Key: SOLR-16046
> URL: https://issues.apache.org/jira/browse/SOLR-16046
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Houston Putman
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the {{TestLeaderElectionZkExpiry.testLeaderElectionWithZkExpiry}}
> test fails roughly 11% of the time due to zombie threads.
> These are {{zkConnectionManagerCallback}} threads used by the SolrZkClient.
> In {{ConnectionManager.process()}}, the method being called by the thread, it
> is currently swallowing up an interrupted exception and always looping until
> a valid connection can be made to zookeeper.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
