[
https://issues.apache.org/jira/browse/HDFS-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706469#comment-13706469
]
Suresh Srinivas commented on HDFS-4942:
---------------------------------------
bq. Suresh, it looks like the issue is rapidly spreading into multiple jiras. I
counted 8 by now.
I have 1 or 2 more jiras to add to this.
The changes are being done in small increments. Each of the part can be done
independently, without rendering trunk in a non-working state. Hence the work
is happening in trunk. Doing it in small increments helps in multiple people
collaborating on this, instead of one person working on a single large, hard to
review patch.
bq. Otherwise porting of the feature in other branches becomes challenging as
cherry picking of multiple patches interleaved with other changes is non-trivial
Sorry I do not understand what the issue is. How does it make porting of the
feature hard?
> 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
