hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4797) RPC Server can leave a lot of direct buffers
Date Mon, 08 Dec 2008 04:42:44 GMT

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

Raghu Angadi commented on HADOOP-4797:
--------------------------------------


Thanks Stack. I will check javadoc again, would appreciate any specific fixes there.

Updated patch has a small fix : '{{ret <= 0}}' is replaced by '{{ret < ioSize}}'. This
avoids extra system call incase of partial i/o (or extra blocking in case of blocking sockets).


> RPC Server can leave a lot of direct buffers 
> ---------------------------------------------
>
>                 Key: HADOOP-4797
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4797
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.17.0
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>         Attachments: HADOOP-4797-branch-18.patch, HADOOP-4797-branch-18.patch
>
>
> RPC server unwittingly can soft-leak direct buffers. One observed case is that one of
the namenodes at Yahoo took 40GB of virtual memory though it was configured for 24GB memory.
Most of the memory outside Java heap expected to be direct buffers. This shown to be because
of how RPC server reads and writes serialized data. The cause and proposed fix are in following
comment.
>   

-- 
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