hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5074) Allow starting up from an fsimage checkpoint in the middle of a segment
Date Wed, 11 Dec 2013 01:30:07 GMT

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

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

Pretty confident that the test failure is unrelated - the balancer tests have been flaky with
timeouts for a long time and I just ran all of the balancer tests on my local box with this
patch applied and they all completed successfully.

+1, the latest patch looks good to me. I'm going to commit this momentarily.

> Allow starting up from an fsimage checkpoint in the middle of a segment
> -----------------------------------------------------------------------
>
>                 Key: HDFS-5074
>                 URL: https://issues.apache.org/jira/browse/HDFS-5074
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, namenode
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-5074.txt, hdfs-5074.txt
>
>
> We've seen the following behavior a couple times:
> - SBN is running and somehow encounters an error in the middle of replaying an edit log
in the tailer (eg the JN it's reading from crashes)
> - SBN successfully has processed half of the edits in the segment it was reading.
> - SBN saves a checkpoint, which now falls in the middle of a segment, and then restarts
> Upon restart, the SBN will load this checkpoint which falls in the middle of a segment.
{{selectInputStreams}} then fails when the SBN requests a mid-segment txid.
> We should handle this case by downloading the right segment and fast-forwarding to the
correct txid.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message