Speed up DataTierAllocationDecider #78075
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
This decider is quite slow in `allocationAllowed` and shows up in profiling. We should be able to get a much tighter loop with this change that avoids building the list of role names over and over and removes some dead code as well.
elasticmachine
added
the
Team:Data Management
|
Pinging @elastic/es-data-management (Team:Data Management) |
|
Do you happen to know how good are the tests here? I added an exception into |
dakrone
requested changes
Sep 21, 2021
.../main/java/org/elasticsearch/xpack/cluster/routing/allocation/DataTierAllocationDecider.java
Outdated
Show resolved
Hide resolved
.../main/java/org/elasticsearch/xpack/cluster/routing/allocation/DataTierAllocationDecider.java
Outdated
Show resolved
Hide resolved
The tierName argument is a single tier name, rather than comma separated list of zero or more tier names.
|
Great catch, @dakrone, I've added two commits that should address your comments. |
dakrone
approved these changes
Sep 22, 2021
| @@ -192,7 +185,12 @@ private Decision shouldIndexPreferTier(IndexMetadata indexMetadata, Set<Discover | |||
| } | |||
|
|
|||
| public static String[] parseTierList(String tiers) { | |||
| return Strings.tokenizeToStringArray(tiers, ","); | |||
| if (Strings.hasLength(tiers) == false) { | |||
There was a problem hiding this comment.
To avoid an array like [" "] (not that we expect that), maybe we should use:
Suggested change
| if (Strings.hasLength(tiers) == false) { | |
| if (Strings.hasText(tiers) == false) { |
| String[] values = parseTierList(tierSetting); | ||
| for (String value : values) { | ||
| private static boolean allocationAllowed(String tierName, Set<DiscoveryNodeRole> roles) { | ||
| assert Strings.hasLength(tierName) : "tierName must be not null and non-empty, but was [" + tierName + "]"; |
There was a problem hiding this comment.
Same here,
Suggested change
| assert Strings.hasLength(tierName) : "tierName must be not null and non-empty, but was [" + tierName + "]"; | |
| assert Strings.hasText(tierName) : "tierName must be not null and non-empty, but was [" + tierName + "]"; |
…-allocation-decider
|
Jenkins run elasticsearch-ci/part-2 |
|
Thanks Joe + Lee! |
original-brownbear
deleted the
speed-up-data-tier-allocation-decider
branch
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this pull request
Sep 22, 2021
This decider is quite slow in `allocationAllowed` and shows up in profiling. We should be able to get a much tighter loop with this change that avoids building the list of role names over and over and removes some dead code as well. Co-authored-by: Joe Gallo <[email protected]>
original-brownbear
added a commit
that referenced
this pull request
Sep 22, 2021
This decider is quite slow in `allocationAllowed` and shows up in profiling. We should be able to get a much tighter loop with this change that avoids building the list of role names over and over and removes some dead code as well. Co-authored-by: Joe Gallo <[email protected]>
97 tasks
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.
This decider is quite slow in
allocationAllowedand shows up in profiling.We should be able to get a much tighter loop with this change that avoids building
the list of role names over and over and removes some dead code as well.
There's certainly additional speedups possible here though, this just deals with the most obvious issue.