Memory Monitor: Remove explicit GC call, clear cached instead #179
Labels
Comments
|
Memory Monitor: Remove explicit GC call, clear cached instead, closed by 8d3347b. |
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
Closes elastic#179 (cherry picked from commit 7700340) (cherry picked from commit ad68433) (cherry picked from commit f83ffd2)
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
Prevent Ansible errors when shield is not installed/disabled, by providing (empty) default values to users_to_remove, users_to_add, and es_users.
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
Es-Hadoop can error (default), warn or ignore the fields used for quering. fix elastic#179
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…86 (pull request elastic#179) ip_addresses.tfvars edited online with Bitbucket: ttang2's pub IP is changed
costin
pushed a commit
that referenced
this issue
Dec 6, 2022
🤖 Generated PR to keep ESQL development branch up to date
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, when there are memory problems for X amount of time, and things can't be flushed, GC is called. This should not happen. Instead, the caches should be explicitly cleared and GC should not be called. The new
clear_cache_thresholdreplaces thegc_threshold.Also, because of this change, there is no need for a scheduler to run on the soft/weak filter caches.
The text was updated successfully, but these errors were encountered: