Added support for strict role validation #37
Merged
Conversation
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
Sometimes the user might want to restrict Hadoop to only launching tasks on top of resources for the given role, and not accept offers for "*"
There was a problem hiding this comment.
Not so sure about this... perhaps I could assign the role to a property on the scheduler and access that?
|
Looks good, thanks! |
brndnmtthws
added a commit
that referenced
this pull request
Oct 14, 2014
Added support for strict role validation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Sometimes the user might want to restrict Hadoop to only launching tasks on top of resources for the given role.
Currently if the framework joins the cluster in the given role, it will also receive offers for any resources that are not assigned to a specific role.