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

Suresh Srinivas updated HADOOP-5724:
------------------------------------

    Attachment: blockdel-2.patch

New patch with suggested changes. Also I understood your comment about checking 
for null for BlockInfo and have added the check.

Patch passes all the unit tests except TestJobHistory (tracked in HADOOP-5920).

No new tests are added as the existing ones test the functionality already. 
Here is the test-patch result:
{noformat}
     [exec] -1 overall.
     [exec]
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]
     [exec]     -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
     [exec]                         Please justify why no tests are needed for 
this patch.
     [exec]
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec]
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec]
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
     [exec]
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath 
integrity.
     [exec]
     [exec]     +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
{noformat}

> Datanode should report deletion of blocks to Namenode explicitly
> ----------------------------------------------------------------
>
>                 Key: HADOOP-5724
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5724
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.21.0
>
>         Attachments: blockdel-1.patch, blockdel-2.patch, blockdel.patch, 
> blockdel.patch
>
>
> Currently datanode notifies namenode newly added blocks and the blocks that 
> are corrupt. There is no explicit message from the datanode to the namenode 
> to indicate the deletion of blocks. Block reports from the datanode is the 
> only way for the namenode to learn about the deletion of blocks at a 
> datanode. With the addition of explicit request to indicate to block 
> deletion, block report interval (which is currently 1 hour) can be increased 
> to a longer duration. This reduces load on both namenode and datanodes.
>  

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

Reply via email to