Coordinator slight optimization of load rule runner to skip drop if numToDrop is 0 #5928
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
jihoonson
approved these changes
Jul 3, 2018
gianm
pushed a commit
to implydata/druid-public
that referenced
this pull request
Jul 5, 2018
jihoonson
pushed a commit
to jihoonson/druid
that referenced
this pull request
Jul 9, 2018
jihoonson
added a commit
that referenced
this pull request
Jul 9, 2018
leventov
pushed a commit
to metamx/druid
that referenced
this pull request
Jul 20, 2018
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 skips filtering the list of servers and the cost balancer
pickServersToDropthat operates on that filtered list of servers that currently always happens even if we are not going to drop any segments.