elastic/elasticsearch

Make SnapshotHistoryStore retry indexing history data on EsRejectedExecutionException

Open

#141887 opened on Feb 4, 2026

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Java (76,700 stars) (25,882 forks)batch import
:Distributed/SLM>bugTeam:Distributedgood first issue

Description

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.

Contributor guide

Tech stack
java
Domain
backenddata
Issue type
bug
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.
1-3 hours
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
JavaElasticsearch source code setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
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.