hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6594) [API] Introduce SchedulingRequest object
Date Mon, 10 Jul 2017 21:37:00 GMT

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

Wangda Tan commented on YARN-6594:

[~kkaranasos], chatted with [~jianhe] offline. I think Jian's concern is more about how AM
use the new feature:

Existing applications interact with YARN by leveraging AMRMClient, however AMRMClient is mostly
design to support MR-like workload, and its design has many issues such as in-consistent resource-request
table between server/client. I think now it is a good opportunity to think about how to fix
the last-mile problem. Do you think we should leverage AMRMClient or we should create a brand-new
ApplicationMaster Java API? I personally prefer to create a new one, to me maintenance of
 legacy code to support new features is much harder than adding a new implementation.

> [API] Introduce SchedulingRequest object
> ----------------------------------------
>                 Key: YARN-6594
>                 URL: https://issues.apache.org/jira/browse/YARN-6594
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Konstantinos Karanasos
>            Assignee: Konstantinos Karanasos
>         Attachments: YARN-6594.001.patch
> This JIRA introduces a new SchedulingRequest object.
> It will be part of the {{AllocateRequest}} and will be used to define sizing (e.g., number
of allocations, size of allocations) and placement constraints for allocations.
> Applications can use either this new object (when rich placement constraints are required)
or the existing {{ResourceRequest}} object.

This message was sent by Atlassian JIRA

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

View raw message