[
https://issues.apache.org/jira/browse/SOLR-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-5492:
----------------------------------------
Attachment: SOLR-5492.patch
I chose to return the actual address as another item in the shards.info
response instead of re-ordering the key string. For example:
{code}
"192.168.43.52:8983/solr/collection1/|192.168.43.52:7584/solr/collection1/": {
"numFound": 14,
"maxScore": 1,
"shardAddress": "http://192.168.43.52:8983/solr/collection1/";,
"time": 5
}
{code}
> Return the replica that actually served the query as the first one in
> shards.info
> ---------------------------------------------------------------------------------
>
> Key: SOLR-5492
> URL: https://issues.apache.org/jira/browse/SOLR-5492
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 5.0, 4.7
>
> Attachments: SOLR-5492.patch
>
>
> The shards.info returns all the replicas in the shard that returned the
> response but it is impossible to figure out which replica was actually used.
> I propose to change the order of the replica list such that the first replica
> in the pipe-separated list is always the one which served the request.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
