You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Benjamin Teke (Jira)" <ji...@apache.org> on 2022/03/23 17:18:00 UTC
[jira] [Comment Edited] (YARN-10549) Decouple RM runner logic from SLSRunner
[ https://issues.apache.org/jira/browse/YARN-10549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511391#comment-17511391 ]
Benjamin Teke edited comment on YARN-10549 at 3/23/22, 5:17 PM:
----------------------------------------------------------------
Thanks [~snemeth] for the patch. At first glance the patch in general looks good to me, however it doesn't apply to trunk even with YARN-10547 + YARN-10552 applied. Maybe I missed something, can you please check?
was (Author: bteke):
Thanks [~snemeth] for the patch. At first glance the patch in general looks good to me, however it doesn't apply to trunk. Maybe I missed something, can you please check?
> Decouple RM runner logic from SLSRunner
> ---------------------------------------
>
> Key: YARN-10549
> URL: https://issues.apache.org/jira/browse/YARN-10549
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Szilard Nemeth
> Assignee: Szilard Nemeth
> Priority: Minor
> Attachments: YARN-10549.001.patch
>
>
> SLSRunner has too many responsibilities.
> One of them is to parse the job details from the SLS input formats and launch the AMs and task containers.
> The RM runner logic could be decoupled.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org