hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2088) Move edits log archiving logic into FSEditLog/JournalManager
Date Wed, 22 Jun 2011 00:12:48 GMT

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

Todd Lipcon commented on HDFS-2088:
-----------------------------------

ah.. good catch. The javadoc is actually wrong. It should be "the maximum transaction ID that
is allowed to be purged". The logic is that if we have an fsimage_123, then that file includes
all data up to and including txid 123. Hence we can purge edits_1-123 safely. I will update
javadoc and post a new patch.

> Move edits log archiving logic into FSEditLog/JournalManager
> ------------------------------------------------------------
>
>                 Key: HDFS-2088
>                 URL: https://issues.apache.org/jira/browse/HDFS-2088
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: Edit log branch (HDFS-1073)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: Edit log branch (HDFS-1073)
>
>         Attachments: hdfs-2088.txt
>
>
> Currently the logic to archive edits logs is File-specific which presents some issues
for Ivan's work. Since it relies on inspecting storage directories using NNStorage.inspectStorageDirs,
it also misses directories that the image layer considers "failed" which results in edits
logs piling up in these kinds of directories. This JIRA is similar to HDFS-2018 but only deals
with archival for now.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message