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 "Eric Badger (JIRA)" <ji...@apache.org> on 2016/09/16 16:44:20 UTC
[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after
container is complete
[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Badger updated YARN-5641:
------------------------------
Attachment: YARN-5641.001.patch
Attaching a patch that creates a separate thread to read the input stream instead of doing it in the main localizer thread. This way the main thread can get interrupted during process.waitFor() and destroy the child threads in the finally block. I tested this using a sleep command instead of the tar command and it killed the sleep command when the localizer was killed.
> Localizer leaves behind tarballs after container is complete
> ------------------------------------------------------------
>
> Key: YARN-5641
> URL: https://issues.apache.org/jira/browse/YARN-5641
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Eric Badger
> Assignee: Eric Badger
> Attachments: YARN-5641.001.patch
>
>
> The localizer sometimes fails to clean up extracted tarballs leaving large footprints that persist on the nodes indefinitely.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org