[
https://issues.apache.org/jira/browse/SOLR-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643444#action_12643444
]
Noble Paul commented on SOLR-565:
---------------------------------
It seems less useful if I assign 1 url for one shard . No a lot more useful
than what it is now.This actually imposes the user to use a loadbalancer
Ideally the shards.properties can have something like this
{code}
#comma separated values per host
shard1=host1:port/solr,host2:port/solr
shard2=host3:port/solr,host4:port/solr
shard3=host5:port/solr,host6:port/solr
{code}
The distributed search should internally do a round-robin between each host for
a shard
> Component to abstract shards from clients
> -----------------------------------------
>
> Key: SOLR-565
> URL: https://issues.apache.org/jira/browse/SOLR-565
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 1.3
> Reporter: patrick o'leary
> Assignee: Otis Gospodnetic
> Priority: Minor
> Fix For: 1.4
>
> Attachments: distributor_component.patch, SOLR-565.patch
>
>
> A component that will remove the need for calling clients to provide the
> shards parameter for
> a distributed search.
> As systems grow, it's better to manage shards with in solr, rather than
> managing each client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
