hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11323) WritableComparator#compare keeps reference to byte array
Date Thu, 20 Nov 2014 19:11:34 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219814#comment-14219814
] 

Hudson commented on HADOOP-11323:
---------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #6581 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/6581/])
HADOOP-11323. WritableComparator#compare keeps reference to byte array. Contributed by Wilfred
Spiegelenburg. (wang: rev eb4045e7652be6ceaf9dfd33e9139d67774b99ab)
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/WritableComparator.java
* hadoop-common-project/hadoop-common/CHANGES.txt


> WritableComparator#compare keeps reference to byte array
> --------------------------------------------------------
>
>                 Key: HADOOP-11323
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11323
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: performance
>    Affects Versions: 2.5.0
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>             Fix For: 2.7.0
>
>         Attachments: HADOOP-11323.patch
>
>
> When the default compare is used on a WritableComparator a reference to the second passed
in byte array is kept in the buffer. Since WritableComparator keeps a reference to the buffer
the byte will never be garbage collected. This can lead to a higher heap use than needed.
> The buffer should drop the reference to the byte array passed in. We can null out the
byte array reference since the buffer is a private variable for the class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message