Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 18 Jul 2013 18:56:50 +0000 (UTC)
From: "Jing Zhao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12658577.1374170245052.75201.1374173810887@arcas>
In-Reply-To: <JIRA.12658577.1374170245052@arcas>
References: <JIRA.12658577.1374170245052@arcas>
Subject: [jira] [Updated] (HDFS-5008) Make ClientProtocol#abandonBlock()
 idempotent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jing Zhao updated HDFS-5008:
----------------------------

    Affects Version/s: 3.0.0
               Status: Patch Available  (was: Open)
    
> 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
>
>
> 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