[
https://issues.apache.org/jira/browse/HDFS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258633#comment-13258633
]
Bikas Saha commented on HDFS-3092:
----------------------------------
@Todd
The definition in the doc for ParallelWritesWithBarrier is deliberately
shallow. The point was just to differentiate between waiting and not waiting.
The doc does not go into specifics of algorithms. So your feedback for
different issues should be directed to the proposal you are commenting on. On
future improvements - again, the doc is meant to be a comparison of the
proposals as we saw them in the design docs submitted to the jira's and
bookkeeper online references.
Basically, going by existing documentation of proposals, the doc tries to
outline the high level salient points to consider.
@Flavio
Thanks for the roadmap pointer.
> 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: ComparisonofApproachesforHAJournals.pdf,
> MultipleSharedJournals.pdf, MultipleSharedJournals.pdf,
> 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
