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