Skip to content

Memory Monitor: Remove explicit GC call, clear cached instead #179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
kimchy opened this issue May 17, 2010 · 1 comment
Closed

Memory Monitor: Remove explicit GC call, clear cached instead #179

kimchy opened this issue May 17, 2010 · 1 comment
Labels
>enhancement v0.08.0

Comments

@kimchy
Copy link
Member

kimchy commented May 17, 2010

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_threshold replaces the gc_threshold.

Also, because of this change, there is no need for a scheduler to run on the soft/weak filter caches.
@kimchy
Copy link
Member Author

kimchy commented May 17, 2010

Memory Monitor: Remove explicit GC call, clear cached instead, closed by 8d3347b.

@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
@dadoonet
Fix mapping examples in documentation
c65db1a 
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
@jakommo
Merge pull request elastic#179 from veger/fix_disabled_shield
127f890 
Prevent Ansible errors when shield is not installed/disabled, by providing (empty) default values to users_to_remove, users_to_add, and es_users.
costin pushed a commit that referenced this issue Dec 6, 2022
@elasticsearchmachine
🤖 ESQL: Merge upstream (#179)
9d4987e 
🤖 Generated PR to keep ESQL development branch up to date
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v0.08.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy