hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4979) Implement retry cache on the namenode
Date Thu, 18 Jul 2013 04:14:48 GMT

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

Suresh Srinivas updated HDFS-4979:
----------------------------------

    Attachment: HDFS-4979.5.patch

Updated patch to fix failures and complete retry cache for all the following operations:

*ClientProtocol*
* create()
* append()
* rename()
* concat()
* rename2()
* delete()
* saveNamespace() - this can be made idempotent, if writeLock is held in this operation
* createSymlink()
* updatePipeline()
* createSnapshot()
* deleteSnapshot()
* renameSnapshot()
* mkdirs() - was incorrectly marked as idempotent

*NamenodeProtocol*
* startCheckpoint()
* endCheckpoint()
* commitBlockSynchronized()

*DatanodeProtocol*
* blockReceivedAndDeleted()

Note that mkdirs() was previously incorrectly marked as idempotent. I plan on removing the
idempotent annotation for that method in HDFS-4974.
                
> Implement retry cache on the namenode
> -------------------------------------
>
>                 Key: HDFS-4979
>                 URL: https://issues.apache.org/jira/browse/HDFS-4979
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: HDFS-4979.1.patch, HDFS-4979.2.patch, HDFS-4979.3.patch, HDFS-4979.4.patch,
HDFS-4979.5.patch, HDFS-4979.patch
>
>


--
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

Mime
View raw message