[
https://issues.apache.org/jira/browse/HDFS-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-3799:
------------------------------
Attachment: hdfs-3799.txt
The solution is as follows:
- during recovery, when we validate a log, if the log has no transactions, then
we remove the file (same as if the log segment was never started)
- when coordinating recovery, if none of the loggers have any non-empty logs,
then we don't have to take any action. We can simply treat the recovery as a
no-op.
> QJM: handle empty log segments during recovery
> ----------------------------------------------
>
> Key: HDFS-3799
> URL: https://issues.apache.org/jira/browse/HDFS-3799
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha
> Affects Versions: QuorumJournalManager (HDFS-3077)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-3799.txt
>
>
> One of the cases not yet handled in the QJM branch is the one where either
> the writer or the journal node crashes after startLogSegment() but before it
> has written its first transaction to the log. We currently have TODO
> assertions in the code which fire in these cases.
> This JIRA is to deal with these cases.
--
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
