[8.0] Disable deprecation log indexing until templates are loaded backport(#80406)#80529
Merged
pgomulka merged 1 commit intoelastic:8.0from Nov 10, 2021
Merged
Conversation
…80406) Deprecation log indexing relies on index templates to be present in cluster state in order to create a data stream. If a very early deprecation is emitted after node is started up and templates are not loaded yet this can result in regular index with default settings and mappings to be created. To prevent this a bulk processor used for indexing deprecation logs delays flushing until templates are loaded. closes elastic#80265
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
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.
Deprecation log indexing relies on index templates to be present in
cluster state in order to create a data stream.
If a very early deprecation is emitted after node is started up and
templates are not loaded yet this can result in regular index with
default settings and mappings to be created.
To prevent this a bulk processor used for indexing deprecation logs
delays flushing until templates are loaded.
closes #80265
gradle check?