[
https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141566#comment-15141566
]
Mark Miller commented on SOLR-8416:
-----------------------------------
bq. Are they pointing to the same exception?
rsp.getException happens when the response is not code 200 okay - but the
collections API works a little different in that sometimes it will put failures
and exceptions in a call that returns 200 okay. We just check both cases.
bq. Also there seems a typo error that return is not included.
Not waiting for individual replicas that did not create is left as a TODO
there, we don't want to do anything yet.
I also moved the waiting code to the CollectionsHandler. I think it's more
efficient and 'safer' to pull the waiting out of the Overseer processing.
I think we can commit this as a good start and use further JIRA's to make any
improvements.
> The collections create API should return after all replicas are active.
> ------------------------------------------------------------------------
>
> Key: SOLR-8416
> URL: https://issues.apache.org/jira/browse/SOLR-8416
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Michael Sun
> Assignee: Mark Miller
> Attachments: SOLR-8416.patch, SOLR-8416.patch, SOLR-8416.patch,
> SOLR-8416.patch, SOLR-8416.patch, 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]
