[
https://issues.apache.org/jira/browse/YARN-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702526#comment-16702526
]
Chandni Singh commented on YARN-8867:
-------------------------------------
[~eyang] With Yarn Service, currently we request for resources to be localized
only while launching a container. Once the component instance is READY, its
localization status is updated. Since the resources were localized with the
container launch, its resources have already finished localization. To be able
to view PENDING localizationStatus, we need the additional capability in YARN
service to localize resource on demand.
Plan to do this in an iterative fashion. The current changes in Yarn Service
were done to easily test this new protocol between AM and NM.
> Retrieve the status of resource localization
> --------------------------------------------
>
> Key: YARN-8867
> URL: https://issues.apache.org/jira/browse/YARN-8867
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Priority: Major
> Attachments: YARN-8867.001.patch, YARN-8867.002.patch,
> YARN-8867.003.patch, YARN-8867.004.patch, YARN-8867.005.patch,
> YARN-8867.006.patch, YARN-8867.wip.patch
>
>
> Refer YARN-3854.
> Currently NM does not have an API to retrieve the status of localization.
> Unless the client can know when the localization of a resource is complete
> irrespective of the type of the resource, it cannot take any appropriate
> action.
> We need an API in {{ContainerManagementProtocol}} to retrieve the status on
> the localization.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
