-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Add cache support in TransportGetAllocationStatsAction
#124898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
1625c13
Add cache support in TransportGetAllocationStatsAction
JeremyDahlgren 8db340e
Switch to controlled time in unit test, address code review comments
JeremyDahlgren dd05487
Refactor lambda passed to deduplicator to check cache in transport th…
JeremyDahlgren 81e32c1
Use timestampMillis name in CachedAllocationStats record
JeremyDahlgren 5d71e1f
Make the cache TTL a dynamic setting
JeremyDahlgren ae438b9
Fix testReturnsOnlyRequestedStats after merging 124902
JeremyDahlgren 341cd9c
Address code review comments
JeremyDahlgren 2e6e6ad
Add documentation for cluster.routing.allocation.stats.cache.ttl
JeremyDahlgren 4555ca2
Update docs/changelog/124898.yaml
JeremyDahlgren File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| pr: 124898 | ||
| summary: Add cache support in `TransportGetAllocationStatsAction` | ||
| area: Allocation | ||
| type: enhancement | ||
| issues: | ||
| - 110716 |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What visibility/exposure should this setting have? I saw other
cluster.routing.allocation.*settings indocsincluster-level-shard-allocation-routing-settings.md. Should it be documented there?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we need to add documentation, either in this PR or in follow up. Both are fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++ would prefer to add the docs in the same PR, otherwise it tends to get forgotten