[
https://issues.apache.org/jira/browse/HADOOP-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe updated HADOOP-10587:
------------------------------------------
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
I think we should hold off on this, since it should not be a problem in
practice. The out-of-memory case that prompted this turned out to be a case
where the heap was entirely filled with tokens, and the DataOutputBuffer
objects were a red herring.
> Use a thread-local cache in TokenIdentifier#getBytes to avoid creating many
> DataOutputBuffer objects
> ----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-10587
> URL: https://issues.apache.org/jira/browse/HADOOP-10587
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.4.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Attachments: HADOOP-10587.001.patch
>
>
> We can use a thread-local cache in TokenIdentifier#getBytes to avoid creating
> many DataOutputBuffer objects. This will reduce our memory usage (for
> example, when loading edit logs), and help prevent OOMs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
