hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6460) Namenode runs of out of memory due to memory leak in ipc Server
Date Wed, 23 Dec 2009 18:42:30 GMT

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

Suresh Srinivas commented on HADOOP-6460:
-----------------------------------------

buf.count() assuming you mean length of underlying byte array size is not exposed by ByteArrayOutputStream.
setupResponse() is also called for Server.authFailedResponse. I do not think that grows to
a large size, but having the log in setup response will make it generic for all streams. 

> Namenode runs of out of memory due to memory leak in ipc Server
> ---------------------------------------------------------------
>
>                 Key: HADOOP-6460
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6460
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.20.1, 0.21.0, 0.22.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 0.20.2, 0.21.0, 0.22.0
>
>         Attachments: hadoop-6460.1.patch, hadoop-6460.5.patch, hadoop-6460.6.patch, hadoop-6460.patch
>
>
> Namenode heap usage grows disproportional to the number objects supports (files, directories
and blocks). Based on heap dump analysis, this is due to large growth in ByteArrayOutputStream
allocated in o.a.h.ipc.Server.Handler.run().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message