[
https://issues.apache.org/jira/browse/SOLR-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Grama updated SOLR-7566:
-------------------------------
Attachment: SOLR-7566-test-code-cosmetics.patch
[~shalinmangar] thank you for setting up the test case. It looks very good and
is straightforward to read. I've taken the liberty of doing some code cosmetics
on it.It's up to you whether you include them in SVN.
> Search requests should return the shard name that is down
> ---------------------------------------------------------
>
> Key: SOLR-7566
> URL: https://issues.apache.org/jira/browse/SOLR-7566
> Project: Solr
> Issue Type: Bug
> Components: search, SolrCloud
> Affects Versions: 5.1
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Trivial
> Fix For: 5.3, Trunk
>
> Attachments: SOLR-7566-test-code-cosmetics.patch, SOLR-7566.patch,
> SOLR-7566.patch, SOLR-7566.patch
>
>
> If no replicas of a shard are up and running, a search request gives the
> following response:
> {code}
> {
> "responseHeader": {
> "status": 503,
> "QTime": 2,
> "params": {
> "q": "*:*",
> "indent": "true",
> "wt": "json",
> "_": "1432048084930"
> }
> },
> "error": {
> "msg": "no servers hosting shard: ",
> "code": 503
> }
> }
> {code}
> The message should mention the shard which is down/unreachable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
