Closed
Conversation
a88a4b7 to
afe98af
Compare
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.
This PR adds an extension for implementing the first version of task tiering as proposed in
https://groups.google.com/d/msg/druid-development/1I3CmxlOipM/e3-SpWqG170J
This is still a work in progress but I wanted to make sure it was available if people want to see where its going.
It depends on some changes to baseline druid, which I will try to keep track of here:
Move resource managemnt to be the responsibility of the TaskRunner #1953 - Moving resource control to the task runnerUse Worker instead of ZkWorker whenever possible #2249 - moving ZkWorker to a Worker wherever possible.Add hashCode and equals to DruidNode #2248 - DruidNode hashCode and equalsI'll flesh out the master comment some more as the PR gets closer to being ready to merge.