[
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.009.patch
bq. It should be either java.util.concurrent.ConcurrentHashMap (and store
something bogus for the value) or just wrap it in a SynchronizedSet.
Wrapped the HashSet inside of a SynchronizedSet.
bq. I'm curious why the random and localDirs fields of
ContainerLocalizerWrapper are marked protected but the others are not? Do they
need to be marked protected?
This was a relic of when I was moving things around trying to limit scope. They
don't need to be protected.
Checkstyle also wants me to make all of the variables private and give them
accessor methods instead of doing the wrapper.* access. I can fix this if you
want.
Attaching new patch
> 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,
> YARN-5641.003.patch, YARN-5641.004.patch, YARN-5641.005.patch,
> YARN-5641.006.patch, YARN-5641.007.patch, YARN-5641.008.patch,
> YARN-5641.009.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
