Add hint about elasticsearch index recreate#1188
Open
marcbachmann wants to merge 1 commit into
Open
Conversation
…be problematic on production
arddor
approved these changes
Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The release-2026-07 Elasticsearch index recreation step read like a quick command. On production,
elasticsearch-index --recreatedeletes the index and repopulates it via a background re-indexing job, during which search returns partial results. Operators need to know this upfront so they plan a maintenance window instead of running it blindly.Changelog
{{< info >}}box warning that--recreatedeletes the index and repopulates it in a background job, returning partial results until it finishes.--handle=<type>to the example and advise running it per handle (drafts, publications, media library) within a maintenance window.