[
https://issues.apache.org/jira/browse/SOLR-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796760#action_12796760
]
Yonik Seeley edited comment on SOLR-1698 at 1/5/10 5:13 PM:
------------------------------------------------------------
Another big question is: can we use LBHttpSolrServer for this, or are the needs
too different?
Some of the issues:
- need control over order (so same server will be used in a single request)
- if we have a big cluster (100 shards), we don't want every node or every
core to have 100 background threads checking liveness
- one request may want to hit addresses [A,B] while another may want [A,B,C] -
a single LBHttpSolrServer can't currently do both at once, and separate
instances wouldn't share liveness info.
One way: have many LBHttpSolrServer instances (one per shard group) but have
them share certain things like the liveness of a shard and the background
cleaning threads
Another way: have a single static LBHttpSolrServer instance that's shared for
all requests, with an extra method that allows passing of a list of addresses
on a per-request basis.
was (Author: ysee...@gmail.com):
Another big question is: can we use LBHttpSolrServer for this, or are the
needs too different?
> load balanced distributed search
> --------------------------------
>
> Key: SOLR-1698
> URL: https://issues.apache.org/jira/browse/SOLR-1698
> Project: Solr
> Issue Type: Improvement
> Reporter: Yonik Seeley
>
> Provide syntax and implementation of load-balancing across shard replicas.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
