hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3313) create a protocol for journal service synchronziation
Date Wed, 25 Apr 2012 18:46:22 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261929#comment-13261929
] 

Aaron T. Myers commented on HDFS-3313:
--------------------------------------

bq. One refactoring we can do is to remove getEditLogManifes() from namenode protocol and
let namenode use JournalSyncProtocol. This is similar as the one Aaron suggested, with the
difference that we won't have a protocol supportting only getEditLogManifes() just to reduce
dup code.

Sure, that'll work until you want to add more methods to the JournalSyncProtocol that don't
make sense for the NN to implement.
                
> create a protocol for journal service synchronziation  
> -------------------------------------------------------
>
>                 Key: HDFS-3313
>                 URL: https://issues.apache.org/jira/browse/HDFS-3313
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>             Fix For: Shared journals (HDFS-3092)
>
>         Attachments: HDFS-3313.HDFS-3092.patch, HDFS-3313.HDFS-3092.patch
>
>
> This protocol is used to synchronize lagging journal service with active journal service
with complete finalized edit segments. Currently it supports one rpc call getEditLogManifest()
which lists finalized edit segments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message