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 43D9AD3A3 for ; Fri, 6 Jul 2012 18:40:37 +0000 (UTC) Received: (qmail 74712 invoked by uid 500); 6 Jul 2012 18:40:35 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 74609 invoked by uid 500); 6 Jul 2012 18:40:35 -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 74433 invoked by uid 99); 6 Jul 2012 18:40:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2012 18:40:34 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id B004A142855 for ; Fri, 6 Jul 2012 18:40:34 +0000 (UTC) Date: Fri, 6 Jul 2012 18:40:34 +0000 (UTC) From: "Brahma Reddy Battula (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <234393774.15326.1341600034722.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (HDFS-3605) Missing Block in following sceanrio. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Brahma Reddy Battula created HDFS-3605: ------------------------------------------ Summary: Missing Block in following sceanrio. Key: HDFS-3605 URL: https://issues.apache.org/jira/browse/HDFS-3605 Project: Hadoop HDFS Issue Type: Bug Components: name-node Affects Versions: 2.0.0-alpha, 2.0.1-alpha Reporter: Brahma Reddy Battula Open file for append Write data and sync. After next log roll and editlog tailing in standbyNN close the append stream. Call append multiple times on the same file, before next editlog roll. Now abruptly kill the current active namenode. Here block this block missed.. this may be because of All latest blocks were queued in StandBy Namenode. During failover, first OP_CLOSE was processing the pending queue and adding the block to corrupted block. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira