hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2972) HA: small optimization building incremental block report
Date Thu, 23 Feb 2012 12:55:49 GMT

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

Hudson commented on HDFS-2972:

Integrated in Hadoop-Hdfs-HAbranch-build #86 (See [https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/86/])
    HDFS-2972. Small optimization building incremental block report. Contributed by Todd Lipcon.
(Revision 1292497)

     Result = UNSTABLE
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1292497
Files : 
* /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/CHANGES.HDFS-1623.txt
* /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BPServiceActor.java

> HA: small optimization building incremental block report
> --------------------------------------------------------
>                 Key: HDFS-2972
>                 URL: https://issues.apache.org/jira/browse/HDFS-2972
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: data-node, ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: HA branch (HDFS-1623)
>         Attachments: hdfs-2972.txt
> Current the incremental block report is a List. However, we only really need to send
the most recent information for each block. So, if a block becomes RBW and is then becomes
FINALIZED before the next incremental block report, we should just report the FINALIZED replica.
It's an easy change to just switch to a map by blockid.
> This is on the HA branch since HA changes the code to send RBWs in the incremental reports,
hence it's more important for maintaining performance parity with trunk.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message