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 "Eric Payne (Jira)" <ji...@apache.org> on 2020/10/26 17:42:00 UTC

[jira] [Commented] (YARN-10431) [Umbrella] Job group management

    [ https://issues.apache.org/jira/browse/YARN-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220868#comment-17220868 ] 

Eric Payne commented on YARN-10431:
-----------------------------------

[~wjlei], does [Oozie|http://oozie.apache.org] meet the same requirements as this Umbrella JIRA? If not, can you please provide input on what Oozie is lacking?

> [Umbrella] Job group management
> -------------------------------
>
>                 Key: YARN-10431
>                 URL: https://issues.apache.org/jira/browse/YARN-10431
>             Project: Hadoop YARN
>          Issue Type: New Feature
>    Affects Versions: 2.9.2
>            Reporter: jialei weng
>            Priority: Major
>         Attachments: YarnJobGroupImpl design.pdf
>
>
> In current yarn job management, we don't have an efficient mechanism to manage several jobs together. For example, one batch job may trigger several sub-jobs to running at the same time, like one job to process the data and another one monitor job metrics. And when we want to cancel these jobs, we have to kill them one by one in current design. I proposal a job group concept to handle such parent-child jobs as one unit.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org