elastic/elasticsearch

SecurityMigrationExecutor and SystemIndexMigrationExecutor should not be persistent tasks

Open

#146.662 aberto em 17 de abr. de 2026

Ver no GitHub
 (3 comments) (0 reactions) (0 assignees)Java (76.700 stars) (25.882 forks)batch import
:Distributed/DistributedTeam:Distributedgood first issue

Description

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

Guia do colaborador

Pilha de tecnologia
java
Domain
backend
Tipo Issue
refactor
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
4
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
over 1 week
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
active
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Understanding of Elasticsearch task execution frameworkJava development experience
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
20
Direção de pesquisa
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.