[
https://issues.apache.org/jira/browse/HDFS-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130463#comment-13130463
]
Ivan Kelly commented on HDFS-1975:
----------------------------------
General direction looks good. I've a few comments.
There's a comma in configuration key.
In FSEditLog, check the states before transitioning them.
Im not sure the tailer will work as is. What happens if you open an inprogress
input stream with this? As I understand it, you'll end up with lastTxnId in the
middle of the segment.
In stopReadingEditLogs(), instead of doing the start stop, to ensure up to
dateness, you could have a call on EditLogTailer#applyLatestUpdates(). Then
EditLogTailerThread could call this in the loop also.
> HA: Support for sharing the namenode state from active to standby.
> ------------------------------------------------------------------
>
> Key: HDFS-1975
> URL: https://issues.apache.org/jira/browse/HDFS-1975
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Reporter: Suresh Srinivas
> Assignee: Jitendra Nath Pandey
> Attachments: HDFS-1975-HA.patch, hdfs-1975.txt, hdfs-1975.txt
>
>
> To enable hot standby namenode, the standby node must have current
> information for - namenode state (image + edits) and block location
> information. This jira addresses keeping the namenode state current in the
> standby node. To do this, the proposed solution in this jira is to use a
> shared storage to store the namenode state.
> Note one could also build an alternative solution by augmenting the backup
> node. A seperate jira could explore this.
--
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
