[SOLR-6714] Collection RELOAD returns 200 even when some shards fail to reload -- other APIs with similar problems?

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: SolrCloud
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 06/Nov/14 20:40
• Updated: 19/Nov/18 21:06

Description

Using 4.10.2, if you startup a simple 2 node cloud with...

./bin/solr start -e cloud -noprompt

And then try to force a situation where a replica is hozed like this...

rm -rf node1/solr/gettingstarted_shard1_replica1/*
chmod a-rw node1/solr/gettingstarted_shard1_replica1

The result of a Collection RELOAD command is still a success...

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>

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.

Issue Links

• is related to: SOLR-6595 Improve error response in case distributed collection cmd fails
• is related to: SOLR-5970 Create collection API always has status 0