hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state
Date Fri, 05 Apr 2013 15:15:16 GMT

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

Hitesh Shah updated YARN-547:
-----------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: YARN-543
    
> 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
in DOWNLOADING state.

--
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

Mime
View raw message