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 "Zhankun Tang (JIRA)" <ji...@apache.org> on 2017/06/19 03:18:00 UTC
[jira] [Updated] (YARN-6720) Support updating FPGA related
constraint node label after FPGA device re-configuration
[ https://issues.apache.org/jira/browse/YARN-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhankun Tang updated YARN-6720:
-------------------------------
External issue ID: YARN-3409
> Support updating FPGA related constraint node label after FPGA device re-configuration
> --------------------------------------------------------------------------------------
>
> Key: YARN-6720
> URL: https://issues.apache.org/jira/browse/YARN-6720
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Zhankun Tang
>
> In order to provide a global optimal scheduling for mutable FPGA resource, it seems an easy and direct way to utilize constraint node labels(YARN-3409) instead of extending the global scheduler(YARN-3926) to match both resource count and attributes.
> The rough idea is that the AM sets the constraint node label expression to request containers on the nodes whose FPGA devices has the matching IP, and then NM resource handler update the node constraint label if there's FPGA device re-configuration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org