[
https://issues.apache.org/jira/browse/YARN-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941390#comment-15941390
]
Carlo Curino commented on YARN-6363:
------------------------------------
[~wangda] in the last (v2) patch, I tried to make the SLSRunner to be a Tool,
and fixed some of the shutdown logic, RM and SLSWebApp were not shutdown so I
was getting port bind issues when I tried to make TestSLSRunner parametrized.
Can you please check if that makes sense to you (I was in a rush)?
Also I changed the commandline params to be more flexible on the tracetype (we
should add an example rumen trace for TestSLSRunner) and I need to double check
after the switch to Tool that this works. Are you ok with this new format?
(using toolRunner we can probably do better with confs as welll).
Also I think it would be nice to have a quick way to configure which ports to
use (instead of a list in sls-runner.xml), because I think it would be nice to
be able to run the SLSRunner in a map-only job where each mapper runs a
different parametrization of the RM (ideal for parameter sweeps).
Please share your thoughts. I will write up a bit about the configuration for
the synth generator in the meantime.
> Extending SLS: Synthetic Load Generator
> ---------------------------------------
>
> Key: YARN-6363
> URL: https://issues.apache.org/jira/browse/YARN-6363
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Carlo Curino
> Assignee: Carlo Curino
> Attachments: YARN-6363.v0.patch, YARN-6363.v1.patch,
> YARN-6363.v2.patch
>
>
> This JIRA tracks the introduction of a synthetic load generator in the SLS.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
