[
https://issues.apache.org/jira/browse/YARN-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671864#comment-16671864
]
Chandni Singh commented on YARN-8867:
-------------------------------------
[~eyang] To find the resources which haven't yet started downloading is quite
cumbersome currently. There are existing limitations in the current code of
{{ResourceLocalizationService}} and {{LocalizedResource}}. Some of which are:
# {{LocalizedResource}} state does not differentiate between resources that are
queued and the ones which are actually in-progress. For both of them, the state
is {{DOWNLOADING}}
# In {{ResourceLocalizationService.LocalizerRunner}}, the {{pending}}
collection holds the resources that are queued as well as submitted. Items from
this list is not removed even when they are submitted. They are removed only
when the state changes from {{DOWNLOADING}} to localized or localization failed.
This will require quite a bit of change in the existing code to differentiate
between resources which are queued and ones which are in-progress. I can create
a new jira for that.
For the change in this jira, should we change IN_PROGRESS to PENDING?
> 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.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: [email protected]
For additional commands, e-mail: [email protected]
