nik Seeley
> Sent: Wed 27-Jun-2012 18:27
> To: solr-user@lucene.apache.org
> Subject: Re: SolrCloud cache warming issues
>
> On Wed, Jun 27, 2012 at 12:23 PM, Erik Hatcher wrote:
> >
> > On Jun 27, 2012, at 12:01 , Yonik Seeley wrote:
> >
> >> On Tue, Jun 2
On Wed, Jun 27, 2012 at 12:23 PM, Erik Hatcher wrote:
>
> On Jun 27, 2012, at 12:01 , Yonik Seeley wrote:
>
>> On Tue, Jun 26, 2012 at 6:53 AM, Markus Jelsma
>> wrote:
>>> Why would the documentCache not be populated via firstSearcher warming
>>> queries with a non-zero value for rows?
>>
>> Sol
On Jun 27, 2012, at 12:01 , Yonik Seeley wrote:
> On Tue, Jun 26, 2012 at 6:53 AM, Markus Jelsma
> wrote:
>> Why would the documentCache not be populated via firstSearcher warming
>> queries with a non-zero value for rows?
>
> Solr streams documents (the stored fields) returned to the user (so
On Tue, Jun 26, 2012 at 6:53 AM, Markus Jelsma
wrote:
> Why would the documentCache not be populated via firstSearcher warming
> queries with a non-zero value for rows?
Solr streams documents (the stored fields) returned to the user (so
very large result sets can be supported w/o having the whol
Hi,
We have about 500 top queries for each core in our test cluster. They are
routed to the default request handler and are not distributed, facetting is
enabled and most common filters are present and rows not specified but the
default is 10. After server start up we only see a few items being
