hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Badger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete
Date Fri, 16 Sep 2016 21:43:20 GMT

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

This new patch should fix most, if not all, of the test failures. The tests were failing because
they were unable to get the IOException that came from parseExecResult(). Since it was in
a child thread, the parent thread didn't have an exception to throw up the stack to the test.


It would be cleaner to also include the errThread as an ExecutorService in the thread pool,
but I've left it as its own standalone thread for now to keep the size of the patch down.
If there is agreement, I can unify them into the same thread pool for consistency. 

> 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, YARN-5641.002.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


Mime
View raw message