Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <20659679.263731284768214407.JavaMail.jira@thor>
Date: Fri, 17 Sep 2010 20:03:34 -0400 (EDT)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-1400) HDFS federation: Introduced block pool
 ID into DataTransferProtocol
In-Reply-To: <27205993.188731284497673678.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas updated HDFS-1400:
----------------------------------

    Attachment: HDFS-1400.trunk.patch

Thanks for the review. Attached is the trunk version of the patch.

A block has two pieces of information.
# Block identifier: this include Block ID and Generation Stamp.
# Block attribute/information: len

I have introduced writeId() and readId() methods to serialize/deserialize only identifier part of Block to be used in DataTransferProtocol.


> HDFS federation: Introduced block pool ID into DataTransferProtocol
> -------------------------------------------------------------------
>
>                 Key: HDFS-1400
>                 URL: https://issues.apache.org/jira/browse/HDFS-1400
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>    Affects Versions: Federation Branch
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: Federation Branch
>
>         Attachments: HDFS-1400.patch, HDFS-1400.trunk.patch
>
>
> Block Pool ID needs to be introduced in to DataTransferProtocol

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