[
https://issues.apache.org/jira/browse/YARN-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379579#comment-16379579
]
Arun Suresh commented on YARN-7929:
-----------------------------------
bq. it looks to me like the O containers are still launched based on the
allocated resource instead of the actual utilization right?
yup
I just saw the bit regarding {{yarn.nodemanager.resource.utilization.ratio}}. I
agree, we need to think a bit more before we incorporate this. Just to clarify,
with this patch, irrespective of what this ratio is, if an AM requests an OPP
containers, it will get the token and a container will be launched right ? I
can buy the argument that the SLS is technically supposed to simulate the
"scheduler" so we can defer actually fixing the NMSimulator to later.
So, think we can go ahead with the commit - but to truly simulate a cluster, we
need YARN-6826
> SLS supports setting container execution
> ----------------------------------------
>
> Key: YARN-7929
> URL: https://issues.apache.org/jira/browse/YARN-7929
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler-load-simulator
> Reporter: Jiandan Yang
> Assignee: Jiandan Yang
> Priority: Major
> Attachments: YARN-7929.001.patch, YARN-7929.002.patch,
> YARN-7929.003.patch, YARN-7929.004.patch, YARN-7929.005.patch,
> YARN-7929.006.patch
>
>
> SLS currently support three tracetype, SYNTH, SLS and RUMEN, but trace file
> can not set execution type of container.
> This jira will introduce execution type in SLS to help better simulation.
> This will help the perf testing with regarding to the Opportunistic
> Containers.
> RUMEN has default execution type GUARANTEED
> SYNTH set execution type by field map_execution_type and
> reduce_execution_type
> SLS set execution type by field container.execution_type
> For compatibility set GUARANTEED as default value when not setting above
> fields in trace file
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
