hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1583) Improve backup-node sync performance by wrapping RPC parameters
Date Mon, 21 Mar 2011 21:42:06 GMT

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

Matt Foley commented on HDFS-1583:
----------------------------------

HADOOP-6949 has been accepted and committed.  Respectfully recommend that HDFS-1583-2.patch
be withdrawn and this bug resolved as Fixed.

> Improve backup-node sync performance by wrapping RPC parameters
> ---------------------------------------------------------------
>
>                 Key: HDFS-1583
>                 URL: https://issues.apache.org/jira/browse/HDFS-1583
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: Liyin Liang
>            Assignee: Liyin Liang
>             Fix For: 0.23.0
>
>         Attachments: HDFS-1583-1.patch, HDFS-1583-2.patch, test-rpc.diff
>
>
> The journal edit records are sent by the active name-node to the backup-node with RPC:
> {code:}
>   public void journal(NamenodeRegistration registration,
>                       int jAction,
>                       int length,
>                       byte[] records) throws IOException;
> {code}
> During the name-node throughput benchmark, the size of byte array _records_ is around
*8000*.  Then the serialization and deserialization is time-consuming. I wrote a simple application
to test RPC with byte array parameter. When the size got to 8000, each RPC call need about
6 ms. While name-node sync 8k byte to local disk only need  0.3~0.4ms.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message