elastic/elasticsearch

SecurityMigrationExecutor and SystemIndexMigrationExecutor should not be persistent tasks

Open

#146.662 geöffnet am 17. Apr. 2026

Auf GitHub ansehen
 (3 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Java (76.700 Stars) (25.882 Forks)batch import
:Distributed/DistributedTeam:Distributedgood first issue

Beschreibung

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

Contributor Guide

Tech Stack
java
Domain
backend
Issue Type
refactor
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
4
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
over 1 week
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
active
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
mostly clear
Voraussetzungen
Understanding of Elasticsearch task execution frameworkJava development experience
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
20
Research-Richtung
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.