elastic/elasticsearch

Make SnapshotHistoryStore retry indexing history data on EsRejectedExecutionException

Open

#141,887 建立於 2026年2月4日

在 GitHub 查看
 (7 留言) (0 反應) (0 負責人)Java (76,700 star) (25,882 fork)batch import
:Distributed/SLM>bugTeam:Distributedgood first issue

描述

ILMHistoryStore uses BulkProcessor to retry indexing history up to 3 times if it hits a EsRejectedExecutionException because the cluster was too busy. From what I can tell, SnapshotHistoryStore just makes a single attempt, and logs an error and moves on if it hits EsRejectedExecutionException. I have seen this several times in production logs. We ought to have SnapshotHistoryStore use BulkProcessor to make a few attempts before giving up.

貢獻者指南

技術棧
java
領域
backenddata
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaElasticsearch source code setup
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
The issue references ILMHistoryStore.java (line 167) using BulkProcessor to retry indexing, while SnapshotHistoryStore.java (line 82) only makes a single attempt. The solution involves adding a similar BulkProcessor with retry logic to SnapshotHistoryStore. Examine the existing ILMHistoryStore implementation and adapt it, ensuring to handle EsRejectedExecutionException properly. Integration tests should be included to verify the retry behavior.
Make SnapshotHistoryStore retry indexing history data on EsRejectedExecutionException · elastic/elasticsearch#141887 | Good First Issue