hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5008) Make ClientProtocol#abandonBlock() idempotent
Date Thu, 18 Jul 2013 19:10:48 GMT

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

Jing Zhao updated HDFS-5008:

    Attachment: HDFS-5008.002.patch

Update the patch: if the block is no longer in the file, we do not need to persist the blocks
in edit log.

Also FSDirectory#unprotectedRemoveBlock is also called while applying edit log for OP_ADD
and OP_CLOSE. The current patch still throws Exception if the block is not in the file in
these two cases.
> Make ClientProtocol#abandonBlock() idempotent
> ---------------------------------------------
>                 Key: HDFS-5008
>                 URL: https://issues.apache.org/jira/browse/HDFS-5008
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Suresh Srinivas
>            Assignee: Jing Zhao
>         Attachments: HDFS-5008.001.patch, HDFS-5008.002.patch
> Currently when abandonBlock is called, if the block does not exist, then the namenode
throws an exception. I propose making it idempotent, by returning success if the block that
is being abandoned does not exist.
> Thoughts?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message