Yonik Seeley
Sent: Thursday, August 07, 2008 5:41 PM
To: solr-user@lucene.apache.org
Subject: Re: Distributed Search Strategy / Shards
On Thu, Aug 7, 2008 at 8:36 PM, CameronL <[EMAIL PROTECTED]>
wrote:
> Does this seem like an issue that might need to be escalated to jira?
Absolute
On Thu, Aug 7, 2008 at 8:36 PM, CameronL <[EMAIL PROTECTED]> wrote:
> Does this seem like an issue that might need to be escalated to jira?
Absolutely.
> We
> might be able to provide you some additional info relating to these threads
> locking if you need it.
Yes, some thread dumps or anything
oming
requests, distributing those to the shards, and merging the results, but I
see by this post:
http://www.nabble.com/Distributed-Search-Caching-td16851547.html#a16884618
That it doesn't seem to be the intended design.
Does this seem like an issue that might need to be escalated to jira? We
On Thu, Aug 7, 2008 at 7:32 PM, CameronL <[EMAIL PROTECTED]> wrote:
>
> What is the current strategy for doing distributed search for Solr? We
> currently have our index divided over 3 servers:
> solr1
> solr2
> solr3
>
> In order to balance the load, our application calls each with a 'shards'
> p
g back the
response.
Is this the intended design for distributed search for solr?
--
View this message in context:
http://www.nabble.com/Distributed-Search-Strategy---Shards-tp18882112p18882112.html
Sent from the Solr - User mailing list archive at Nabble.com.
