On 3/23/2012 9:55 AM, stockii wrote:
how look your requestHandler of your broker? i think about your idea to do
the same ;)
Here's what I have got for the default request handler in my broker
core, which is called ncmain. The "rollingStatistics" section is
applicable to the SOLR-1972 patch.
000
- Solr1 for Search-Requests - commit every Minute - 5GB Xmx
- Solr2 for Update-Request - delta every Minute - 4GB Xmx
--
View this message in context:
http://lucene.472066.n3.nabble.com/querying-on-shards-tp3841446p3852001.html
Sent from the Solr - User mailing list archive at Nabble.com.
I'd _really_ recommend that you do not do this unless and
until it's provably necessary. As Shawn says, the load on the
shards that return nothing will probably be very low. And
this is the kind of thing that one spends endless hours
debugging. Somehow, sometime, I flat guarantee you'll
be trying t
On 3/19/2012 11:55 PM, Ankita Patil wrote:
Hi,
I wanted to know whether it is feasible to query on all the shards even if
the query yields data only from a few shards n not all. Or is it better to
mention those shards explicitly from which we get the data and only query
on them.
for example :
I
Hi,
I wanted to know whether it is feasible to query on all the shards even if
the query yields data only from a few shards n not all. Or is it better to
mention those shards explicitly from which we get the data and only query
on them.
for example :
I have 4 shards. Now I have a query which yiel
