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-2973) HA: re-enable NO_ACK optimization for block deletion
Date Thu, 23 Feb 2012 12:55:49 GMT

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

Hudson commented on HDFS-2973:

Integrated in Hadoop-Hdfs-HAbranch-build #86 (See [https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/86/])
    HDFS-2973. Re-enable NO_ACK optimization for block deletion. Contributed by Todd Lipcon.
(Revision 1292611)

     Result = UNSTABLE
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1292611
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/blockmanagement/BlockManager.java
* /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestHASafeMode.java

> HA: re-enable NO_ACK optimization for block deletion
> ----------------------------------------------------
>                 Key: HDFS-2973
>                 URL: https://issues.apache.org/jira/browse/HDFS-2973
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: HA branch (HDFS-1623)
>         Attachments: hdfs-2973.txt
> Currently in trunk, when a file is removed, the deletion request is sent to the DNs with
a special NO_ACK flag to indicate that they don't need to ACK the deletion. The NN itself
takes care of removing the blocks from the block map, so the deletion report would be redundant.
> In the HA branch, we disabled this to fix a failure in TestSafeMode -- when the active
NN issues a block deletion, and the standby hasn't read the edits yet, this test case expects
that it would see the block deletions.
> I don't see any actual compelling reasons for this. I think we can restore the optimization
and modify the test to pass.

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