You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Omkar Vinit Joshi (JIRA)" <ji...@apache.org> on 2013/04/05 07:56:15 UTC

[jira] [Created] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

Omkar Vinit Joshi created YARN-547:
--------------------------------------

             Summary: 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: Bug
            Reporter: 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