[
https://issues.apache.org/jira/browse/SOLR-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583399#comment-14583399
]
Shalin Shekhar Mangar commented on SOLR-7566:
---------------------------------------------
bq. The patch attached to this issue checks already within
HttpShardHandler.checkDistributed method whether a shard doesn't have any
active replicas.
I am sorry, I misread your earlier patch. I thought that you were checking the
complete URL string instead of one slice's URL string. You should also handle
the shards.tolerant parameter (see ShardParams.SHARDS_TOLERANT). If this param
is true then we cannot throw an exception in HttpShardHandler.checkDistributed
and we should continue with the empty string.
> 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
> Priority: Trivial
> Fix For: 5.2, Trunk
>
> Attachments: 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]
