[
https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060441#comment-15060441
]
Mark Miller commented on SOLR-8416:
-----------------------------------
bq. 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.
I agree, the complication is probably not worth it.
bq. Is it good to be a solr config or collection config?
I would make it a solr config - we need that ease of use at least. Later, if
someone wants to override per collection or something, we can look at adding
that in a way that you can override.
> 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: [email protected]
For additional commands, e-mail: [email protected]
