[
https://issues.apache.org/jira/browse/HDFS-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204765#comment-13204765
]
Todd Lipcon commented on HDFS-2909:
-----------------------------------
{quote}
Say everything is healthy and FSImage.rollEditLogs() is called.
It first calls FSEditLogs.rollLogs that actually rolls the logs.
It then calls storage.writeTransactionIdFileToStorage() which records this in
all storage dirs so that the information about the rolled edits is not lost.
However, NN could crash in after FSEditLogs.rollLogs() has completed and before
storage.writeTransactionIdFileToStorage() is called. That might leave the data
in an inconsistent state.
{quote}
I don't think this inconsistent state is problematic. The requirement is that
we don't log any actual edits to the new edit log until it's been recorded in
all of the storage directories. In the case of the crash you described, you
might be able to start up without the new edit log segment, but that edit log
segment would be empty anyway.
> HA: Inaccessible shared edits dir not getting removed from FSImage storage
> dirs upon error
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-2909
> URL: https://issues.apache.org/jira/browse/HDFS-2909
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
--
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
