elastic/elasticsearch

Automatically release resources when scrolls are entirely consumed

Open

#23269 opened on Feb 20, 2017

View on GitHub
 (6 comments) (2 reactions) (0 assignees)Java (76,700 stars) (25,882 forks)batch import
:Search Foundations/Search>enhancementTeam:Search Foundationshelp wanted

Description

Automatically closing scroll contexts when they are entirely consumed proved controversial as it would make subsequent DELETE calls return a 404 error code. However, we could release associated resources without deleting it.

Contributor guide

Tech stack
javarest api
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaKnowledge of Elasticsearch scrolls
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the controversy around automatically closing scrolls after consumption. Investigate how to release associated resources (e.g., memory, file handles) without deleting the scroll context. Look at the current scroll implementation in Elasticsearch's search module. Consider modifying the scroll lifecycle to allow resource cleanup while keeping the context alive for DELETE calls.