Skip to content
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

Time Memory Leak: Search requests don't eagerly clean the search context #153

Closed
kimchy opened this issue Apr 29, 2010 · 1 comment
Closed

Time Memory Leak: Search requests don't eagerly clean the search context #153

kimchy opened this issue Apr 29, 2010 · 1 comment
Labels
>bug v0.07.0

Comments

@kimchy
Copy link
Member

kimchy commented Apr 29, 2010

When executing a search request, they don't get eagerly cleaned properly, which means they will get cleaned after the default keep alive timeout (5 minutes). Under heavy search load, this might cause memory problems.
@kimchy
Copy link
Member Author

kimchy commented Apr 29, 2010

Time Memory Leak: Search requests don't eagerly clean the search context, closed by 30aae50.

@bluelu bluelu mentioned this issue Dec 11, 2014
Closed
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
@jinhucheung jinhucheung mentioned this issue Aug 14, 2018
Closed
@patrykk21 patrykk21 mentioned this issue Oct 2, 2018
Closed
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
@jakommo
Merge pull request elastic#153 from jakommo/master
c2dede8 
Added LICENSE file.
@Hailei Hailei mentioned this issue Mar 16, 2021
Closed
costin pushed a commit that referenced this issue Dec 6, 2022
Applying the changes introduced in #87504 to the ESQL code base (#153)
80c1f5b
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@dliappis
Fail early if any locally attached physical disks are not ok
6eb0203 
Flash memory storage can also fail, typically when erase cycles have
exceeded a threshold.

In this commit we add a fixture that checks all locally attached
physical disks across all nodes, via smartctl, and fails
if the self-assessment result is not OK.

This check can be skipped through the FIXTURES env var.

Relates: elastic#153
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
>bug v0.07.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy