[
https://issues.apache.org/jira/browse/YARN-8670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588925#comment-16588925
]
Weiwei Yang commented on YARN-8670:
-----------------------------------
Hi [~Sichen Zhao]
{quote}it seems all the improvements is depending on YARN-3409?
{quote}
Only if you want to specify node-attributes, that will depend on YARN-3409.
Good news is that branch is close to merge, we are trying to get it done in 2 -
3 weeks.
{quote}PC and allocataiontags shouldn't add to container level.
{quote}
The PC is specified in SchedulingRequest, so it is request level. It should be
enough right?
{quote}So maybe we need create a new task class. PC, allocataiontags and
taskcontainer are members of task class
{quote}
Before going into the implementation details, I would love to know your idea
how to specify PC in request level. Curren SLS supports to launch workload from
SLS/Rumen/Synth traces. YARN-8007 was to support in Synth traces, so it was
only able to test simple affinity/anti-affinity PCs. Therefore, could you
please share the idea to support a large number of jobs/requests with PCs in
traces?
Thanks
> Support scheduling request for SLS input and attributes for Node in SLS
> -----------------------------------------------------------------------
>
> Key: YARN-8670
> URL: https://issues.apache.org/jira/browse/YARN-8670
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler-load-simulator
> Affects Versions: YARN-3409
> Reporter: Sichen zhao
> Priority: Major
> Fix For: YARN-3409
>
>
> YARN-3409 introduces placement constraint, Currently SLS does not support
> specify placement constraint.
> YARN-8007 support specifying placement constraint for task containers in SLS.
> But there are still
> some room for improvement:
> # YARN-8007 only support placement constraint for the jobs level. In fact,
> the more flexible way is support placement constraint for the tasks level.
> # In most scenarios, node itself has some characteristics, called attribute,
> which is not supported in SLS. So we can add the attribute on Nodes.
> # YARN-8007 use the SYNTH as schedulingrequest input. But SYNTH can't create
> a large number of specific resource requests. We wanna create a new
> schedulingrequest input format(like sis format) for the more authentic input.
> We can add some field in sis format, and this is schedulingrequest input
> format.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
