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] [Updated] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state
Date Mon, 15 Apr 2013 18:10:16 GMT

     [ https://issues.apache.org/jira/browse/YARN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Omkar Vinit Joshi updated YARN-547:

    Attachment: yarn-547-20130415.patch

Fixing failed test cases. 
> 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
>         Attachments: yarn-547-20130411.1.patch, yarn-547-20130411.patch, yarn-547-20130412.patch,
> 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