[
https://issues.apache.org/jira/browse/HDFS-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845006#comment-13845006
]
Hudson commented on HDFS-5074:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4861 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4861/])
Move entry for HDFS-5074 to correct section. (atm:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1550027)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> 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
> Fix For: 2.3.0
>
> 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)
