You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Kuhu Shukla (JIRA)" <ji...@apache.org> on 2017/05/24 20:03:04 UTC
[jira] [Updated] (YARN-6641) Non-public resource localization on a
bad disk causes subsequent containers failure
[ https://issues.apache.org/jira/browse/YARN-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kuhu Shukla updated YARN-6641:
------------------------------
Attachment: YARN-6641.001.patch
v1 patch that calls the constructor for LocalResourceTracker with LocalDirsHandlerService object. It dies that also in the case where it is trying to recover resources.
> Non-public resource localization on a bad disk causes subsequent containers failure
> -----------------------------------------------------------------------------------
>
> Key: YARN-6641
> URL: https://issues.apache.org/jira/browse/YARN-6641
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.8.0
> Reporter: Kuhu Shukla
> Assignee: Kuhu Shukla
> Attachments: YARN-6641.001.patch
>
>
> YARN-3591 added the {{checkLocalResource}} method to {{isResourcePresent()}} call to allow checking an already localized resource against the list of good/full directories.
> Since LocalResourcesTrackerImpl instantiations for app level resources and private resources do not use the new constructor, such resources that are on bad disk will never be checked against good dirs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org