Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 22 Mar 2011 06:03:06 +0000 (UTC)
From: "Liyin Liang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <88895791.3339.1300773786350.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <30335292.336331294897726069.JavaMail.jira@thor>
Subject: [jira] [Resolved] (HDFS-1583) Improve backup-node sync performance
 by wrapping RPC parameters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Liyin Liang resolved HDFS-1583.
-------------------------------

    Resolution: Fixed

This bug has been fixed by HADOOP-6949.

> 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