lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: Poor performance on distributed search
Date Sat, 17 Dec 2011 01:18:52 GMT
Right, are you falling afoul of the recursive shard thing? That is,
if you shards point back to itself. As far as I understand, your
shards parameter in your request handler shouldn't point back
to itself....

But I'm guessing here.

Best
Erick

On Fri, Dec 16, 2011 at 4:27 PM, ku3ia <demesg@gmail.com> wrote:
>>> OK, so your speed differences are pretty much dependent upon whether you
> specify
>>> rows=2000 or rows=10, right? Why do you need 2,000 rows?
> Yes, big difference is 10 v. 2K records. Limit of 2K rows is setted by
> manager and I can't decrease it. It is a minimum row count needed to process
> data.
>
>>> Or is the root question why there's such a difference when you specify
>>> qt=requestShards? In which case I'm curious to see that request
>>> handler definition...
>
>  <requestHandler name="requestShards" class="solr.SearchHandler"
> default="false">
>     <lst name="defaults">
>       <str name="echoParams">explicit</str>
>       <int name="rows">10</int>
>       <str
> name="shards">127.0.0.1:8080/solr/shard1,127.0.0.1:8080/solr/shard2,127.0.0.1:8080/solr/shard3,127.0.0.1:8080/solr/shard4</str>
>     </lst>
>    </requestHandler>
>
> This request handler is defined at shard1's solrconfig.
>
> --
> View this message in context: http://lucene.472066.n3.nabble.com/Poor-performance-on-distributed-search-tp3590028p3592734.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Mime
View raw message