[
https://issues.apache.org/jira/browse/YARN-8480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551245#comment-16551245
]
Wangda Tan commented on YARN-8480:
----------------------------------
[~templedf],
{quote}It also looks to me like the PCM is an out-of-band scheduling process
that skips the usual scheduling process.
{quote}
There're two approaches to do PCM allocation, one is called
{{PlacementConstraintProcessor}} it is out-of-band. And the other one is
scheduler, which happens inside normal scheduler loop. You can check
http://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/PlacementConstraints.html
for more details.
When we were doing scheduler changes to placement constraint, we put most
logics to common part like AppSchedulingInfo, so other scheduler impl can use
it directly. The hardest part is done, you only add some glue code to make FS
work.
If you really don't like to utilize the new SchedulingRequest, adding node
attribute to ResourceRequest could be also considered (I'm not quite like the
approach, but it is acceptable to me).
By going with the approach to support node attribute by ResourceRequest,
changes in FS should be minimum and all other logics like how to assign node
attribute to nodes, how node to report node attributes to RM, how web UIs
renders attributes etc. can be reused.
Looping other folks who are doing node attribute support here for more
thoughts: [~sunilg], [~cheersyang], [~Naganarasimha], [~bibinchundatt].
> Add boolean option for resources
> --------------------------------
>
> Key: YARN-8480
> URL: https://issues.apache.org/jira/browse/YARN-8480
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Daniel Templeton
> Assignee: Szilard Nemeth
> Priority: Major
> Attachments: YARN-8480.001.patch, YARN-8480.002.patch
>
>
> Make it possible to define a resource with a boolean value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
