You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2017/05/21 22:40:05 UTC

[jira] [Closed] (SOLR-2132) Distributed query to duplicate shards

     [ https://issues.apache.org/jira/browse/SOLR-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Høydahl closed SOLR-2132.
-----------------------------
    Resolution: Won't Fix

Closing ancient issue as won't fix, since there has not been any traction on this and I believe newer smarter alternatives exist. If anyone still have faith in this particular approach, feel free to re-open.

> Distributed query to duplicate shards
> -------------------------------------
>
>                 Key: SOLR-2132
>                 URL: https://issues.apache.org/jira/browse/SOLR-2132
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>            Reporter: Mike Anderson
>            Priority: Minor
>         Attachments: SOLR-2132.patch
>
>
> I think it would be useful to have the option of specifying shard "sets" in the shards parameter. Such that if all shards in a set are replicating from the same master (and thus have the same documents) the HTTPCommComponent will honor the first shard to respond and not wait for the subsequent shards in the same set. This will improve performance in the use case when one shard is occasionally slow and holds up the entire response. I'm not sure if this is a feature that other people want, but I thought I'd post the code none the less.
> -Mike



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org