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 "Wangda Tan (JIRA)" <ji...@apache.org> on 2016/12/29 20:13:58 UTC
[jira] [Updated] (YARN-6040) Remove usage of ResourceRequest from
AppSchedulerInfo / SchedulerApplicationAttempt
[ https://issues.apache.org/jira/browse/YARN-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wangda Tan updated YARN-6040:
-----------------------------
Summary: Remove usage of ResourceRequest from AppSchedulerInfo / SchedulerApplicationAttempt (was: [YARN-5139] Remove usage of ResourceRequest from AppSchedulerInfo / SchedulerApplicationAttempt)
> Remove usage of ResourceRequest from AppSchedulerInfo / SchedulerApplicationAttempt
> -----------------------------------------------------------------------------------
>
> Key: YARN-6040
> URL: https://issues.apache.org/jira/browse/YARN-6040
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Assignee: Wangda Tan
>
> As mentioned by YARN-5906, currently schedulers are using ResourceRequest heavily so it will be very hard to adopt the new PowerfulResourceRequest (YARN-4902).
> This JIRA is the 2nd step of refactoring, which remove usage of ResourceRequest from AppSchedulingInfo / SchedulerApplicationAttempt. Instead of returning ResourceRequest, it returns a lightweight and API-independent object - {{PendingAsk}}.
> The only remained ResourceRequest API of AppSchedulingInfo will be used by web service to get list of ResourceRequests.
> So after this patch, usage of ResourceRequest will be isolated inside AppSchedulingInfo, so it will be more flexible to update internal data structure and upgrade old ResourceRequest API to new.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org