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

Aaron T. Myers commented on HDFS-1975:
--------------------------------------

Looks like a pretty good first draft, Todd. Since this isn't intended for commit, I didn't review it for style. One question:

Given that the {{lagLenth}} is set to 1000, will there be a problem if an {{FSEditLogOp}} is serialized to more than 1000 bytes? Or if an EOF is encountered in the middle of a serialized op? I suspect some exception might get thrown in this case which would cause the tailer to fail.

> 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.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira