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 Thu, 25 Jul 2013 01:10:46 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.000.patch

Very initial patch just for review (based on the change in HDFS-4979). The patch only adds
RPC clientId and callId to the editlog. Will add the functionality to rebuild the retry cache
based on edit log in the next step.
                
> 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: HDFS-5025.000.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