hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7033) Add support for NM Recovery of assigned resources(GPU's, NUMA, FPGA's) to container
Date Fri, 01 Sep 2017 15:36:01 GMT

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

Devaraj K commented on YARN-7033:

[~sunilg], Thanks again for looking into this.

bq. In NMLeveldbStateStoreService, CONTAINER_ASSIGNED_RESOURCES_KEY_SUFFIX will be updated
only in case of GPU's, NUMA, FPGA's cases correct. If some one adds a custom resource after
YARN-3926, will this code hit ?
Here CONTAINER_ASSIGNED_RESOURCES_KEY_SUFFIX is combined with the resourceType and is used
as key for each container assigned resources of that particular type, It should work for any
resourceType. There is nothing to bind only for these GPU's, NUMA, FPGA's types. Please let
me know if doesn't clarifies or any other thoughts.

> Add support for NM Recovery of assigned resources(GPU's, NUMA, FPGA's) to container
> -----------------------------------------------------------------------------------
>                 Key: YARN-7033
>                 URL: https://issues.apache.org/jira/browse/YARN-7033
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            Reporter: Devaraj K
>            Assignee: Devaraj K
>         Attachments: YARN-7033-v0.patch, YARN-7033-v1.patch, YARN-7033-v2.patch, YARN-7033-v3.patch,
> This JIRA adds the common logic to store the assigned resources to container such as
GPU's(YARN-6620), NUMA(YARN-5764) and FPGA's(YARN-5983) etc. and recover upon restart of NM.

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