[
https://issues.apache.org/jira/browse/SOLR-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089527#comment-14089527
]
Ramkumar Aiyengar commented on SOLR-6336:
-----------------------------------------
bq. other functions in the queue still do this
That's only {{offer}}, which is best managed by the caller as the watcher
depends on the arguments passed in. In any case, that's handled reasonably well
by CollectionsHandler which uses it.
> DistributedQueue (and it's use in OCP) leaks ZK Watches
> -------------------------------------------------------
>
> Key: SOLR-6336
> URL: https://issues.apache.org/jira/browse/SOLR-6336
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Ramkumar Aiyengar
> Assignee: Mark Miller
>
> The current {{DistributedQueue}} implementation leaks ZK watches whenever it
> finds children or times out on finding one. OCP uses this in its event loop
> and can loop tight in some conditions (when exclusivity checks fail), leading
> to lots of watches which get triggered together on the next event (could be a
> while for some activities like shard splitting).
> This gets exposed by SOLR-6261 which spawns a new thread for every parallel
> watch event.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
