[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661705#comment-13661705
]
Sandy Ryza commented on YARN-392:
---------------------------------
As I mentioned, any mechanism that allows whitelisting also allows blacklisting
by definition, as it is always possible to whitelist all the nodes but the one
that one doesn't want. So I don't see it as overloading.
bq. The most common use case of black listing is to specify a set of nodes on
which no allocations should be made
I am not suggesting that this blacklisting mechanism is there to address the
most common case. In the same way that the most common use of delay scheduling
is probably a cluster-wide setting, but allowing customization on specific
requests in the way that you suggested earlier on this thread would still be
useful, the ability to blacklist nodes for specific requests does not preclude
a cluster-wide setting to address the common case.
Does the following seem like a fair representation of the mechanics of the
alternative? When a node-level request comes with disableAllocation=true, an
InvalidAllocationException is thrown. When a rack-level request comes with
disableAllocation=true, we check to make sure that there are nodes under it.
If not, an InvalidAllocationException is thrown. When a node-level request is
cancelled, we check the rack above it to make sure that if its
disableAllocation=true, there are other non-zero node-level requests below it.
If not, we throw an InvalidAllocationException. To me, this seems both more
complicated and gives up functionality unnecessarily. That said, if we can get
some consensus on an alternative, I am happy to implement that instead.
> Make it possible to specify hard locality constraints in resource requests
> --------------------------------------------------------------------------
>
> Key: YARN-392
> URL: https://issues.apache.org/jira/browse/YARN-392
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Sandy Ryza
> Attachments: YARN-392-1.patch, YARN-392-2.patch, YARN-392-2.patch,
> YARN-392-2.patch, YARN-392-3.patch, YARN-392-4.patch, YARN-392.patch
>
>
> Currently its not possible to specify scheduling requests for specific nodes
> and nowhere else. The RM automatically relaxes locality to rack and * and
> assigns non-specified machines to the app.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
