[
https://issues.apache.org/jira/browse/SOLR-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174514#comment-14174514
]
Shawn Heisey commented on SOLR-6336:
------------------------------------
[~mewmewball], because this issue is resolved and you're having what looks to
you like a related bug, it's standard practice to open a new issue. Sometimes
discussion may continue on an issue after it's resolved, typically that would
be for clarification purposes, to decide whether a new issue should be filed.
You can link the new issue to this as a related issue after you create it.
I do not understand the cloud/zookeeper internals well enough to know what you
were saying above. One day I hope to.
> 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
> Fix For: 4.10, Trunk
>
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
