Thanks!
Reinaldo
On Wed, Jun 24, 2020 at 11:47 AM Emir Arnautović <
emir.arnauto...@sematext.com> wrote:
> Hi Reinaldo,
> It is per core. Single node can have cores from different collections,
> each configured differently. When you size caches from memory consumption
> point of view, you have t
Hi Reinaldo,
It is per core. Single node can have cores from different collections, each
configured differently. When you size caches from memory consumption point of
view, you have to take into account how many cores will be placed on each node.
Of course, you have to count replicas as well.
H
: FilterCache:
...
: So if a query contains two fq params, it will create two separate entries
: for each of these fq params. The value of each entry is the list of ids of
: all documents across the index that match the corresponding fq param. Each
: entry is independent of any other entry
Rahul,
Get SPM for Solr from http://sematext.com/spm and you'll get all the insight
into your cache utilization you need and more, and through it you will get
(faster) answers to all your questions if you play with your Solr config
settings and observe cache metrics in SPM.
Otis
Performan
: Is it possible to use solr caches such as query cache , filter cache
: and document cache from external caching system like memcached as it
: has several advantages such as centralized caching system and reducing the
: pause time of JVM 's garbage collection as we can assign less
On Mon, Apr 5, 2010 at 9:10 PM, Chris Hostetter
wrote:
>
>
> : > ... the reusing the FieldCache seems like hte only thing that would be
> : > advantageous in that case
> :
> : And FieldCache entries are currently reused when there have only been
> : deletions on a segment (since Solr 1.4).
>
> But
: > ... the reusing the FieldCache seems like hte only thing that would be
: > advantageous in that case
:
: And FieldCache entries are currently reused when there have only been
: deletions on a segment (since Solr 1.4).
But that's kind of orthoginal to (what i think) Lance's point was: that
On Mon, Apr 5, 2010 at 9:04 PM, Chris Hostetter
wrote:
> ... the reusing the FieldCache seems like hte only thing that would be
> advantageous in that case
And FieldCache entries are currently reused when there have only been
deletions on a segment (since Solr 1.4).
-Yonik
http://www.lucidimagin
: We had exactly this problem in a consumer app; we had a small but
: continuously growing list of obscene documents in the index, and did
: not want to display these. So, we had a filter query with all of the
: obscene words, and used this with every query.
that doesn't seem like it would really
: times. Is there any way to have the index keep its caches when the only thing
: that happens is deletions, then invalidate them when it's time to actually add
: data? It would have to be something I can dynamically change when switching
: between deletions and the daily import.
The problem is
In a word: "no".
What you can do instead of deleting them is to add them to a growing
list of "don't search for these documents". This could be listed in a
filter query.
We had exactly this problem in a consumer app; we had a small but
continuously growing list of obscene documents in the index,
11 matches
Mail list logo
