[
https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061258#comment-15061258
]
Gregory Chanan commented on SOLR-8416:
--------------------------------------
The patch claims to be looking at all shards being active but is actually
looking at all replicas being active, right? It's also inconsistent with the
other creation commands now, e.g. CREATESHARD/ADDREPLICA will return as soon as
the replicas are created while this will wait until all the replicas are active.
>From a client perspective, what do you actually want? I don't think it's that
>all replicas are active at one time; given a large enough cluster that can be
>unlikely. Some possibilities:
1) all the replicas were able to become active (you'd have to track this
separately)
2) the collection is "usable" from the client -- each shard has a leader that
is live and active?
> 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]
