Make SnapshotHistoryStore retry indexing history data on EsRejectedExecutionException · elastic/elasticsearch#141887

(7 comments) (0 reactions) (0 assignees)Java (76,700 stars) (25,882 forks)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
Issue 種別: bug
難度: 3
推定時間: 1-3 hours
活動状況: active
明確さ: clear
前提条件: JavaElasticsearch source code setup
初心者向け度: 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.