[
https://issues.apache.org/jira/browse/SOLR-16909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905590#comment-17905590
]
David Smiley commented on SOLR-16909:
-------------------------------------
Some people (not me) have strong opinions about this -- particularly not
returning a collection that is being constructed. :shrug:. *Perhaps* a
solution might be that a request into a collection that is still being
constructed should block a while long enough until it's sufficiently ready?
Would mean adding a state to a collection I suppose. Hmmm. Another might be,
put in ZK a list of collections being created. Use this to take the set
difference. There could be complexities in ensuring it's removed.
> Collections LIST command should fetch ZK data, not cached state
> ---------------------------------------------------------------
>
> Key: SOLR-16909
> URL: https://issues.apache.org/jira/browse/SOLR-16909
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Major
>
> The LIST command to the Collections API presently returns all collections
> from the cached ClusterState. The proposal here is to fetch the child nodes
> in ZooKeeper instead. While the distinction is minor, the intent is to
> improve robustness / comprehensiveness. It may mean a collection is listed
> that is being created or being deleted that otherwise might not have been
> returned. The scenario driving this is to facilitate cleanup daemons that
> identify potentially left-over data from a collection creation or deletion
> that maybe failed (partial create or delete).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
