[
https://issues.apache.org/jira/browse/SOLR-17895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031438#comment-18031438
]
David Smiley commented on SOLR-17895:
-------------------------------------
Probably not related to Curator. It's up to us to place the lock in ZK where
we want, regardless of implementation. Perhaps these locks should live
underneath the collection znode so that they get cleaned up. But deleting a
collection holds a lock on that collection.
I think a simple solution is using CreateMode.CONTAINER for the parent nodes
holding the Lock. I looked into Curator and it can even do that automatically.
> Persistent ZNodes are leaked when running Solr Cloud with distributed
> collection commands
> -----------------------------------------------------------------------------------------
>
> Key: SOLR-17895
> URL: https://issues.apache.org/jira/browse/SOLR-17895
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 9.0, 10.0
> Reporter: Paul McArthur
> Priority: Minor
>
> When a collection command is executed in distributed mode
> (DistributedCollectionCommandRunner), an ephemeral ZNode is created to lock
> the collection, shard or replica that prevents other commands from executing
> concurrently and potentially conflicting with each other.
>
> The ephemeral nodes are created in a tree structure under
> {_}*distributedapi/collectionlocks*{_}, with persistent znodes created for
> collName
> collName/Locks
> collName/_shard
> collName/_shard/Locks
> collName/_shard/_replica
>
> These nodes are never deleted from ZooKeeper, even when the collection is
> deleted, and can therefore accrue over time.
> In our specific case, we have accumulated many thousands of these nodes over
> a few months. While there appears to be no direct impact on performance,
> these nodes should nonetheless be removed when they are no longer required.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
