Optimize IndexLifecycleMetadata#getPolicies #116988
Merged
Conversation
This file contains 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
rather than on each invocation
joegallo
added
>refactoring
:Data Management/ILM+SLM
|
Pinging @elastic/es-data-management (Team:Data Management) |
|
In some sense, this is a follow up to #115347. |
💚 Backport successful
|
joegallo
added a commit
to joegallo/elasticsearch
that referenced
this pull request
Nov 19, 2024
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 19, 2024
rjernst
pushed a commit
to rjernst/elasticsearch
that referenced
this pull request
Nov 20, 2024
alexey-ivanov-es
pushed a commit
to alexey-ivanov-es/elasticsearch
that referenced
this pull request
Nov 28, 2024
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.
IndexLifecycleMetadata#getPoliciesis (edit: well, 'was') called in a loop inIndexTemplateRegistry#addIndexLifecyclePoliciesIfMissingon every cluster state change -- given that the contents of the map are entirely deterministic and can be pre-calculated atIndexLifecycleMetadataconstruction time, it seemed simple enough to just do that.