[
https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060396#comment-15060396
]
Michael Sun commented on SOLR-8416:
-----------------------------------
A patch is uploaded. Here are some thoughts:
1. The patch pulls shard status from zk and returns if they are all active
during preset time or throw exception. An alternative is to wait for zk
notifications but I am not sure how much is the gain.
2. The total wait time should be configurable to fit large cluster. Is it good
to be a solr config or collection config? It's more natural to be collection
config but it may be easy for user if it's a solr config that can be set in CM.
> Solr collection creation API should return after all cores are alive
> ---------------------------------------------------------------------
>
> Key: SOLR-8416
> URL: https://issues.apache.org/jira/browse/SOLR-8416
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Michael Sun
> Attachments: SOLR-8416.patch
>
>
> Currently the collection creation API returns once all cores are created. In
> large cluster the cores may not be alive for some period of time after cores
> are created. For any thing requested during that period, Solr appears
> unstable and can return failure. Therefore it's better the collection
> creation API waits for all cores to become alive and returns after that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
