hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7457) DatanodeID generates excessive garbage
Date Fri, 16 Jan 2015 15:42:37 GMT

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

Hudson commented on HDFS-7457:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #2026 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2026/])
HDFS-7457. DatanodeID generates excessive garbage. Contributed by Daryn Sharp. (kihwal: rev
780a6bf14562fd9d1070a7c8e756fa1c3bc65d32)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/DatanodeID.java


> DatanodeID generates excessive garbage
> --------------------------------------
>
>                 Key: HDFS-7457
>                 URL: https://issues.apache.org/jira/browse/HDFS-7457
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>             Fix For: 2.7.0
>
>         Attachments: HDFS-7457.patch
>
>
> {{DatanodeID#getXferAddr}} is a dynamically generated string.  This string is repeatedly
generated for the hash code, equality, comparisons, and stringification.  Every DN->NN
RPC method calls {{DatanodeManager#getDatanode}} to validate if the node is registered, which
involves a call to {{getXferAddr}}.
> The dynamic computation generates unnecessary trash that puts unnecessary pressure on
the GC.



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

Mime
View raw message