Thanks, Erick. I will try that
On Sun, Feb 16, 2014 at 5:07 PM, Erick Erickson wrote:
> Stored fields are what the Solr DocumentCache in solrconfig.xml
> is all about.
>
> My general feeling is that stored fields are mostly irrelevant for
> search speed, especially if lazy-loading is enabled.
Stored fields are what the Solr DocumentCache in solrconfig.xml
is all about.
My general feeling is that stored fields are mostly irrelevant for
search speed, especially if lazy-loading is enabled. The only time
stored fields come in to play is when assembling the final result
list, i.e. the 10 or
Thanks Tri
*a. Are you docs distributed evenly across shards: number of docs and size
of the shards*
>> Yes the size of all the shards is equal (an ignorable delta in the order
of KB) and so are the # of docs
*b. Is your test client querying all nodes, or all the queries go to those
2 busy nodes
1. Yes, that's the right way to go, well, in theory at least :)2. Yes, queries are alway fanned to all shards and will be as slow as the slowest shard. When I looked intoSolr distributed querying implementation a few months back, the support for graceful degradation for thingslike network failures
Hell folks
We are currently using solrcloud 4.3.1. We have 8 node solrcloud cluster
with 32 cores, 60Gb of ram and SSDs.We are using zk to manage the
solrconfig used by our collections
We have many collections and some of them are relatively very large
compared to the other. The size of the sha