hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kuhu Shukla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6641) Non-public resource localization on a bad disk causes subsequent containers failure
Date Wed, 24 May 2017 21:54:04 GMT

     [ 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.002.patch

Fixed minor checkstyle issues.  Findbugs warnings are in files this patch has not touched
so leaving them unaddressed for now.

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


Mime
View raw message