The heap allocation and cache settings are per host/JVM not for each collection / shards. In SolrCloud you execute queries against a collection and every other collection may have different schema/document id's and all. So answer to your question, query1 from coll1 can't use results cached from query against coll2.
Thnx On Fri, Jun 2, 2017 at 1:40 AM, Daniel Angelov <dani.b.ange...@gmail.com> wrote: > Is the filter cache separate for each host and then for each collection and > then for each shard and then for each replica in SolrCloud? > For example, on host1 we have, coll1 shard1 replica1 and coll2 shard1 > replica1, on host2 we have, coll1 shard2 replica2 and coll2 shard2 > replica2. Does this mean, that we have 4 filter caches, i.e. separate > memory for each core? > If they are separated and for example, query1 is handling from coll1 shard1 > replica1 and 1 sec later the same query is handling from coll2 shard1 > replica1, this means, that the later query will not use the result set > cached from the first query... > > BR > Daniel >
