hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5024) Make DatanodeProtocol#commitBlockSynchronization idempotent
Date Wed, 24 Jul 2013 22:21:49 GMT

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

Arpit Agarwal updated HDFS-5024:

    Attachment: HDFS-5024.006.patch

Thanks Jing! I have updated the patch to add {{LOG.isDebugEnabled}} calls.
> Make DatanodeProtocol#commitBlockSynchronization idempotent
> -----------------------------------------------------------
>                 Key: HDFS-5024
>                 URL: https://issues.apache.org/jira/browse/HDFS-5024
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>         Attachments: HDFS-5024.001.patch, HDFS-5024.002.patch, HDFS-5024.003.patch, HDFS-5024.004.patch,
HDFS-5024.005.patch, HDFS-5024.006.patch
> commitBlockSynchronization is not idempotent (repeated invocations with the same arguments
will throw an exception). By making it Idempotent we can remove the requirement to track invocations
using the retry cache.

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