elastic/elasticsearch

Automatically release resources when scrolls are entirely consumed

Open

#23,269 创建于 2017年2月20日

在 GitHub 查看
 (6 评论) (2 反应) (0 负责人)Java (76,700 star) (25,882 fork)batch import
:Search Foundations/Search>enhancementTeam:Search Foundationshelp wanted

描述

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.

贡献者指南

技术栈
javarest api
领域
backend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
JavaKnowledge of Elasticsearch scrolls
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
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.
Automatically release resources when scrolls are entirely consumed · elastic/elasticsearch#23269 | Good First Issue