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-4942) Add retry cache support in Namenode
Date Tue, 02 Jul 2013 21:59:21 GMT

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

Suresh Srinivas updated HDFS-4942:
----------------------------------

    Attachment: HDFSRetryCache.pdf

Here is the early version of the design document. Still pending is the analysis of all the
Namenode RPC requests. I will post that soon.

Given that we plan on adding a unique identifier  to every RPC request, should we get this
change done before 2.1.0-beta rc2 is built? This way 2.1.0-beta clients can utilize retry
cache as well.
                
> Add retry cache support in Namenode
> -----------------------------------
>
>                 Key: HDFS-4942
>                 URL: https://issues.apache.org/jira/browse/HDFS-4942
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha, namenode
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: HDFSRetryCache.pdf
>
>
> In current HA mechanism with FailoverProxyProvider and non HA setups with RetryProxy
retry a request from the RPC layer. If the retried request has already been processed at the
namenode, the subsequent attempts fail for non-idempotent operations such as  create, append,
delete, rename etc. This will cause application failures during HA failover, network issues
etc.
> This jira proposes adding retry cache at the namenode to handle these failures. More
details in the comments.

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