And for 10,000 documents across n shards, that can be significant! On May 10, 2013, at 11:43 AM, Joel Bernstein <joels...@gmail.com> wrote:
> How many shards are in your collection? The query aggregator node will pull > pack that results from each shard and hold the results in memory. Then it > will add the results to a priority queue to sort them. This queue will need > to be as large as the page that is being generated. > > After the query is finished this memory should be collectable. > > > On Thu, May 9, 2013 at 8:00 PM, Otis Gospodnetic <otis.gospodne...@gmail.com >> wrote: > >> You are looking at jvm heap but attributing it to caching only. Not quite >> right...there are other things in that jvm heap. >> >> Otis >> Solr & ElasticSearch Support >> http://sematext.com/ >> On May 9, 2013 3:55 PM, "Furkan KAMACI" <furkankam...@gmail.com> wrote: >> >>> I have Solr 4.2.1 and run them as SolrCloud. When I do a search on >>> SolrCloud as like that: >>> >>> ip_of_node_1:8983solr/select?q=*:*&rows=10000 >>> >>> and when I check admin page I see that: >>> >>> I have 5 GB Java Heap. 616.32 MB is dark gray, 3.13 GB is gray. >>> >>> Before my search it was something like: 150 MB dark gray, 500 MB gray. >>> >>> I understand that when I do a search like that, fields are cached. >> However >>> when I look at other SolrCloud nodes' admin pages there are no >> differences. >>> Why that query is cached only by the node that I run that query on? >>> >> > > > > -- > Joel Bernstein > Professional Services LucidWorks
