[
https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061338#comment-15061338
]
Michael Sun commented on SOLR-8416:
-----------------------------------
Yeah. It's not easy to make tradeoff, in particular optimized for large cluster
and high load like this. In addition to looking at other systems, another
choice (which probably always works) is to add an option to allow user to
decide if Solr should wait for all shard leaders to be active or all replicas
at run time.
The additional option need to be documented and adds a bit to the learning
curve for users. But in general it won't create much burden since users usually
are prepared to do some extra optimization for large cluster under high load.
> 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
