hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-509) Redesisn DataNode volumeMap to include all types of Replicas
Date Tue, 04 Aug 2009 22:24:15 GMT

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

Hairong Kuang commented on HDFS-509:

In this patch, the replicas map is a hash map from Long to ReplicaInfo where the key is a
block id. If the patch to HADOOP-512 gets committed, I'd like to change the key to be ReplicaInfo
so eliminating Long objects to be allocated for keys. It will also eliminate the allocation
of a temporary Long object in both get & remove methods.

> Redesisn DataNode volumeMap to include all types of Replicas
> ------------------------------------------------------------
>                 Key: HDFS-509
>                 URL: https://issues.apache.org/jira/browse/HDFS-509
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: data-node
>    Affects Versions: Append Branch
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: Append Branch
>         Attachments: replicas.patch
> With the new append design, replicas at a DataNode could be in one of the five states:
Finalized, ReplicaBeingWritten, ReplicaWaitingToBeRecovered, ReplicaUnderRecovery, and Temporay.
This jira is to
> 1. define the in-memory representation of these five types of replicas
> 2. redefine volumeMap to include all five types of replicas and remove ongoingCreates

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

View raw message