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