elastic/elasticsearch

SecurityMigrationExecutor and SystemIndexMigrationExecutor should not be persistent tasks

Open

#146,662 opened on 2026年4月17日

GitHub で見る
 (3 comments) (0 reactions) (0 assignees)Java (76,700 stars) (25,882 forks)batch import
:Distributed/DistributedTeam:Distributedgood first issue

説明

Both SecurityMigrationExecutor and SystemIndexMigrationExecutor are run-to-completion one-shot migration tasks rather than continuously-running services. They do not "persist" in any meaningful sense, instead they have some external retry mechanism, so it seems that they would better fit as just regular transport actions instead.

Refactoring those task to not be persistent tasks would also get us one step closer to removing the automaticReassignmentOnShutdown() persistent task executor flag (see https://github.com/elastic/elasticsearch/issues/138565) and making this feature default everywhere.

See: https://github.com/elastic/elasticsearch/pull/145753 for more details

コントリビューターガイド

技術スタック
java
領域
backend
Issue 種別
refactor
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
active
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
Understanding of Elasticsearch task execution frameworkJava development experience
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
20
調査方針
Review the linked PR (https://github.com/elastic/elasticsearch/pull/145753) for detailed context on why SecurityMigrationExecutor and SystemIndexMigrationExecutor are currently persistent tasks and how to refactor them to regular transport actions. Examine the `automaticReassignmentOnShutdown()` flag mentioned in issue #138565 to understand the broader goal. The refactoring should ensure that these one shot migration tasks are no longer treated as continuously running services, simplifying the task execution model.