[
https://issues.apache.org/jira/browse/SOLR-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290735#comment-15290735
]
Alan Woodward commented on SOLR-9130:
-------------------------------------
Recovery happens in its own thread, which is presumably why this doesn't cause
a failure on core startup.
There are a bunch of config and schema requirements for cloud (off the top of
my head I can think of: uniqueid and _version_ fields, /get handler and update
log). I think it would be useful to add some checking to the ConfigSetService.
getConfig() could call out to an abstract validate() method, and then
CloudConfigSetService can run its own checks there and throw an exception if
the config won't work in cloud mode. That way we fail fast before a core is
even loaded.
> fail to create cloud collection on RecoveryStrategy ERROR
> ----------------------------------------------------------
>
> Key: SOLR-9130
> URL: https://issues.apache.org/jira/browse/SOLR-9130
> Project: Solr
> Issue Type: Sub-task
> Components: search
> Reporter: Mikhail Khludnev
> Priority: Minor
> Labels: cloud
>
> Spinoff SOLR-9110.
> When I launch a cloud test (but not only test) with non-cloud config eg
> solrconfig-basic.xml from test/resources it logs ERROR somewhere deep in
> logs, but doesn't propagate this error to create collection call
> {noformat}
> ERROR cloud.RecoveryStrategy - No UpdateLog found
> - cannot recover. core=app-analytics
> {noformat}
> Please to consider error propagation and explicit create collection failure
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
