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 4EBF5D456 for ; Wed, 22 Aug 2012 19:06:43 +0000 (UTC) Received: (qmail 55677 invoked by uid 500); 22 Aug 2012 19:06:43 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 55546 invoked by uid 500); 22 Aug 2012 19:06:43 -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 55528 invoked by uid 99); 22 Aug 2012 19:06:42 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 19:06:42 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A54EA2C0919 for ; Wed, 22 Aug 2012 19:06:42 +0000 (UTC) Date: Thu, 23 Aug 2012 06:06:42 +1100 (NCT) From: "Eli Collins (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <2131788625.1906.1345662402677.JavaMail.jiratomcat@arcas> In-Reply-To: <314033100.106182.1343316336038.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0 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-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439766#comment-13439766 ] Eli Collins commented on HDFS-3731: ----------------------------------- Great +1. The code/design makes sense to me and we know the current path is broken and we've verified the fix. Suresh and Nicholas I'll commit this unless you're going to check it out. > 2.0 release upgrade must handle blocks being written from 1.0 > ------------------------------------------------------------- > > Key: HDFS-3731 > URL: https://issues.apache.org/jira/browse/HDFS-3731 > Project: Hadoop HDFS > Issue Type: Bug > Components: data-node > Affects Versions: 2.0.0-alpha > Reporter: Suresh Srinivas > Assignee: Colin Patrick McCabe > Priority: Blocker > Attachments: HDFS-3731.002.patch, HDFS-3731.003.patch > > > Release 2.0 upgrades must handle blocks being written to (bbw) files from 1.0 release. Problem reported by Brahma Reddy. > The {{DataNode}} will only have one block pool after upgrading from a 1.x release. (This is because in the 1.x releases, there were no block pools-- or equivalently, everything was in the same block pool). During the upgrade, we should hardlink the block files from the {{blocksBeingWritten}} directory into the {{rbw}} directory of this block pool. Similarly, on {{-finalize}}, we should delete the {{blocksBeingWritten}} directory. -- 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