[
https://issues.apache.org/jira/browse/SOLR-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132140#comment-18132140
]
Nick Shanin commented on SOLR-6714:
-----------------------------------
>From code reading against apache/main b73f03976fa, the V1 RELOAD path returns
>the result of reloadCollection through squashIntoSolrResponseWithoutHeader
>(solr/core/src/java/org/apache/solr/handler/admin/api/ReloadCollectionAPI.java:67-71,
> 75-85). The open choice is whether a RELOAD with failed replicas should
>return a non-200 status now. Option one changes the status now, which is a
>visible API change for clients that treat 200 as success. Option two waits for
>the status design in SOLR-6595, which would make status meaningful across the
>Collection APIs. Which of these two options do you prefer?
🤖 AI-generated 🤖
> Collection RELOAD returns 200 even when some shards fail to reload -- other
> APIs with similar problems?
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-6714
> URL: https://issues.apache.org/jira/browse/SOLR-6714
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Chris M. Hostetter
> Priority: Major
>
> Using 4.10.2, if you startup a simple 2 node cloud with...
> {noformat}
> ./bin/solr start -e cloud -noprompt
> {noformat}
> And then try to force a situation where a replica is hozed like this...
> {noformat}
> rm -rf node1/solr/gettingstarted_shard1_replica1/*
> chmod a-rw node1/solr/gettingstarted_shard1_replica1
> {noformat}
> The result of a Collection RELOAD command is still a success...
> {noformat}
> curl -sS -D -
> 'http://localhost:8983/solr/admin/collections?action=RELOAD&name=gettingstarted'
> HTTP/1.1 200 OK
> Content-Type: application/xml; charset=UTF-8
> Transfer-Encoding: chunked
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
> <lst name="responseHeader"><int name="status">0</int><int
> name="QTime">1866</int></lst><lst name="failure"><str
> name="127.0.1.1:8983_solr">org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:Error
> handling 'reload' action</str></lst><lst name="success"><lst
> name="127.0.1.1:8983_solr"><lst name="responseHeader"><int
> name="status">0</int><int name="QTime">1631</int></lst></lst><lst
> name="127.0.1.1:7574_solr"><lst name="responseHeader"><int
> name="status">0</int><int name="QTime">1710</int></lst></lst><lst
> name="127.0.1.1:7574_solr"><lst name="responseHeader"><int
> name="status">0</int><int name="QTime">1795</int></lst></lst></lst>
> </response>
> {noformat}
> The HTTP stats code of collection level APIs should not be 200 if any of the
> underlying requests that it depends on result in 4xx or 5xx errors.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
