[
https://issues.apache.org/jira/browse/HDFS-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397099#comment-13397099
]
Todd Lipcon commented on HDFS-3425:
-----------------------------------
bq. Todd, I think you are right. When can you commit your changes?
I'm hoping to have a fully-functional prototype by the end of this week - glad
to finally have some coding time without conferences to worry about ;-)
After that I will do the work to split the changes into more digestible chunks
rather than the big git branch. Since some of the pieces are still in flux I
didn't want to try to start filing individual JIRAs for each item, only to
later find out the interface wasn't quite right.
bq. As Suresh pointed out, the code should be usable by NN and JN to stream
logs from each other (or just between JNs).
Yes, we need to also do the work so that the 2NN can work in a cluster where
the NN has no local edits storage. This implies that the GetImageServlet either
needs to read from the JournalManager API, or the 2NN needs to use the JM API
to transfer edits. I'm not quite sure yet which is the right approach. Do you
have any thoughts on that?
> Enable standby namenode to tail edits from journal service
> ----------------------------------------------------------
>
> Key: HDFS-3425
> URL: https://issues.apache.org/jira/browse/HDFS-3425
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Reporter: Brandon Li
> Assignee: Brandon Li
> Attachments: HDFS-3425.HDFS-3092.patch, HDFS-3425.HDFS-3092.patch.2
>
>
> In an HA cluster with the journal service configured, namenode should get
> edit logs from journal service instead of from local or shared storage
> directories.
> As one of the first steps towards this goal, this JIRA is to enable standby
> namenode to tail edits from journal services.
--
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
