- 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.
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.
are on shards you're not querying.
4 you fixed the problem in 3 on all but one place in the code...
and maybe all of the above at once... G...
This really smells like premature optimization.
Best
Erick
On Tue, Mar 20, 2012 at 10:37 AM, Shawn Heisey s...@elyograg.org wrote:
On 3/19/2012 11:55 PM
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 :
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
