[
https://issues.apache.org/jira/browse/HDFS-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron T. Myers updated HDFS-1975:
---------------------------------
Attachment: HDFS-1975-HDFS-1623.patch
Thanks a ton for your review, Todd. Here's an updated patch which addresses all
of your comments except the following.
bq. In EditLogFileInputStream, why do we need to pass isInProgress as a
boolean? If it's in-progress, that means we don't know the lastTxId, so it
would be INVALID_TXID, right? So we can implement isInProgress() by just
comparing lastTxId.
Because in the case of pre-transactional ELFIS, we pass in INVALID_TXID, even
though the log is not yet in progress.
I'm still working on producing an updated patch which also adds testing for the
pending DN message queues.
> 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.2.patch, HDFS-1975-HA.patch,
> HDFS-1975-HDFS-1623.patch, HDFS-1975-HDFS-1623.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
