Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B58A4109F6 for ; Wed, 28 Aug 2013 01:10:53 +0000 (UTC) Received: (qmail 19865 invoked by uid 500); 28 Aug 2013 01:10:53 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 19833 invoked by uid 500); 28 Aug 2013 01:10:53 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 19823 invoked by uid 99); 28 Aug 2013 01:10:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Aug 2013 01:10:53 +0000 Date: Wed, 28 Aug 2013 01:10:53 +0000 (UTC) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-5074) Allow starting up from an fsimage checkpoint in the middle of a segment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751985#comment-13751985 ] Hadoop QA commented on HDFS-5074: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12600284/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:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/4899//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4899//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 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira