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

Todd Lipcon commented on HDFS-3092:
-----------------------------------

bq. Right now I see a 3K+ line patch in HDFS-3077. Posting such a huge patch 
makes review, code reuse etc. difficult.

I agree. But when I post work piecemeal, I get complaints that it's hard to see 
the overall direction of the work. So not sure how to satisfy folks... Given 
this is all new code, and a lot of it is tests and "protobuf translators", it's 
actually not too bad.

If you will agree to review the pieces as they come in, I'm happy to split 
HDFS-3077 into several patches. But if no one is signing up to review the 
pieces, splitting it up just slows down progress in my experience.
                
> Enable journal protocol based editlog streaming for standby namenode
> --------------------------------------------------------------------
>
>                 Key: HDFS-3092
>                 URL: https://issues.apache.org/jira/browse/HDFS-3092
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha, name-node
>    Affects Versions: 0.24.0, 0.23.3
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: MultipleSharedJournals.pdf
>
>
> Currently standby namenode relies on reading shared editlogs to stay current 
> with the active namenode, for namespace changes. BackupNode used streaming 
> edits from active namenode for doing the same. This jira is to explore using 
> journal protocol based editlog streams for the standby namenode. A daemon in 
> standby will get the editlogs from the active and write it to local edits. To 
> begin with, the existing standby mechanism of reading from a file, will 
> continue to be used, instead of from shared edits, from the local edits.

--
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

        

Reply via email to