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-544) Failed resource localization might introduce a race condition.
Date Wed, 10 Apr 2013 20:01:16 GMT

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

Omkar Vinit Joshi commented on YARN-544:

Yes it gets hanged... I mean resource download never happens for the mentioned scenario as
the resource stays in memory. yarn-539 fix will address this problem too.
> Failed resource localization might introduce a race condition.
> --------------------------------------------------------------
>                 Key: YARN-544
>                 URL: https://issues.apache.org/jira/browse/YARN-544
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Omkar Vinit Joshi
>            Assignee: Omkar Vinit Joshi
> When resource localization fails [Public localizer / LocalizerRunner(Private)] it sends
ContainerResourceFailedEvent to the containers which then sends ResourceReleaseEvent to the
failed resource. In the end when LocalizedResource's ref count drops to 0 its state is changed
> Now if a Resource gets ResourceRequestEvent in between ContainerResourceFailedEvent and
last ResourceReleaseEvent then for that resource ref count will not drop to 0 and the container
which sent the ResourceRequestEvent will keep waiting.

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