[
https://issues.apache.org/jira/browse/HDFS-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838353#comment-13838353
]
Hadoop QA commented on HDFS-5074:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12616850/hdfs-5074.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 10 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs
hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal:
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/5628//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5628//console
This message is automatically generated.
> 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#6144)
