hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Omkar Vinit Joshi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state
Date Thu, 11 Apr 2013 22:13:16 GMT

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

Omkar Vinit Joshi commented on YARN-547:

Fix details :-
* Underlying problem:- Resource was getting requested even when it is in DOWNLOADING state
for ResourceRequestEvent.
* Solution :- Fixing unwanted transition and for RequestEvent in DOWNLOADING state just adds
container in the waiting queue.
* Tests :- Making sure that resource never moves back to INIT state even when requesting container
releases it before localization. In case of Release event when resource is in DOWNLOADING
state just updates container list(ref).
> New resource localization is tried even when Localized Resource is in DOWNLOADING state
> ---------------------------------------------------------------------------------------
>                 Key: YARN-547
>                 URL: https://issues.apache.org/jira/browse/YARN-547
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Omkar Vinit Joshi
>            Assignee: Omkar Vinit Joshi
> At present when multiple containers try to request a localized resource 
> 1) If the resource is not present then first it is created and Resource Localization
starts ( LocalizedResource is in DOWNLOADING state)
> 2) Now if in this state multiple ResourceRequestEvents come in then ResourceLocalizationEvents
are fired for all of them.
> Most of the times it is not resulting into a duplicate resource download but there is
a race condition present there. 
> Location : ResourceLocalizationService.addResource .. addition of the request into "attempts"
in case of an event already exists.
> The root cause for this is the presence of FetchResourceTransition on receiving ResourceRequestEvent

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message