[
https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098194#comment-15098194
]
Mark Miller commented on SOLR-8416:
-----------------------------------
bq. requires injection of delays or failure in core creation which I didn't
find a good way to do
This has been lacking in our test framework for a long time for a variety of
reasons. I recently started working on something to inject faults though - we
have to have it.
Take a look at
https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/java/org/apache/solr/util/TestInjection.java
We should use it carefully, and in the right places, but I think testing
collection creation fail cases fits the bill.
We use assertions to call the fault injection methods so that they cannot be
called by mistake in production (Solr tests require assertions are on, and we
don't properly support running with assertions on in production).
> 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, 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]
