[
https://issues.apache.org/jira/browse/HDFS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244503#comment-13244503
]
Suresh Srinivas commented on HDFS-3092:
---------------------------------------
bq. Could I request that this work be done on a feature branch, as there are
multiple competing proposals to fill the same need? Then, when the features are
complete, we can either choose to merge all, some, or none of them, based on
their merits.
The problem with this is, we could avoid unnecessary duplication effort. Like
we did in HDFS-1623, we could divide the implementation into multiple jiras.
Different people can pickup jiras and contribute. Right now I see a 3K+ line
patch in HDFS-3077. Posting such a huge patch makes review, code reuse etc.
difficult.
For now, perhaps development can happen and we could see if the code reuse can
happen later.
> 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
