[
https://issues.apache.org/jira/browse/HDFS-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723433#comment-13723433
]
Jing Zhao commented on HDFS-5025:
---------------------------------
Thanks Suresh! I've created HDFS-5045 to address the TODO.
I've run some simple manual HA tests in a 6-node cluster, in which I forced NN
failover periodically and kept sending client requests by using LoadGenerator.
Looks like the retry cache works while we still need HADOOP-9792. I will keep
running HA tests on top of branch-2.1.0-beta.
> Record ClientId and CallId in EditLog to enable rebuilding retry cache in
> case of HA failover
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-5025
> URL: https://issues.apache.org/jira/browse/HDFS-5025
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, namenode
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: editsStored, HDFS-5025.000.patch, HDFS-5025.001.patch,
> HDFS-5025.002.patch, HDFS-5025.003.patch, HDFS-5025.004.patch,
> HDFS-5025.005.patch
>
>
> In case of HA failover, we need to be able to rebuild the retry cache in the
> other Namenode. We thus need to record client id and call id in the edit log
> for those "AtMostOnce" operations.
--
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
