elastic/kibana

Cleanup old migration backup indices

Open

#135,721 opened on Jul 5, 2022

View on GitHub
 (4 comments) (3 reactions) (0 assignees)TypeScript (19,065 stars) (8,021 forks)batch import
Feature:MigrationsTeam:Coregood first issue

Description

Upon upgrading Kibana, migrations will create a new index for every new version. Old indices are kept indefinitely. Because these "backup" indices are system indices users should not have to manually clean them up.

Although our documentation has recommended since 7.12+ that users only rollback using snapshots and don't rely on these backup indices, some users might still assume these can replace a snapshot for rollback purposes.

As a result we should probably not remove backup indices until 8.x but introduce a configuration option that defaults to keeping one version's backup indices.

Related to https://github.com/elastic/kibana/issues/126672

Contributor guide

Tech stack
typescript
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Understand Kibana migration systemFamiliarity with Elasticsearch indicesTypeScript experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the current migration backup index handling in Kibana. Look at the related issue #126672 and examine the migration code to understand how indices are created and left behind. Determine where to add a configuration option for cleanup and how to implement the logic to keep only one version's backup indices. Consider backwards compatibility and documentation updates.
Cleanup old migration backup indices · elastic/kibana#135721 | Good First Issue