Hoss Man created SOLR-6714:
------------------------------
Summary: Collection RELOAD returns 200 even when osme hsards 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
Reporter: Hoss Man
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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
