hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5025) Record ClientId and CallId in EditLog to enable rebuilding retry cache in case of HA failover
Date Mon, 29 Jul 2013 23:41:49 GMT

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

Jing Zhao updated HDFS-5025:
----------------------------

    Attachment: HDFS-5025.004.patch

Thanks for the review and comments, Suresh and Colin! Update the patch to address Suresh's
comments. 

For ClientId and UUID part, I added a new class ClientId providing a set of helper methods
converting bytes/string to string/bytes for UUID-based client ID.

The patch depends on HADOOP-9786, thus will trigger Jenkins later.
                
> 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
>
>
> 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

Mime
View raw message