elastic/elasticsearch

Automatically release resources when scrolls are entirely consumed

Open

#23,269 opened on Feb 20, 2017

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

Repository metrics

Stars
 (76,700 stars)
PR merge metrics
 (Avg merge 2d) (1,000 merged PRs in 30d)

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

Research direction
Investigate how scroll contexts are managed and how resources can be released without deleting the context. Look at existing close/delete mechanisms and consider a new API or internal cleanup.
Tech stack
java
Domain
backendapiperformance
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Understanding of Elasticsearch scroll APIJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40