Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 57152 invoked from network); 5 Oct 2010 17:57:03 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Oct 2010 17:57:03 -0000 Received: (qmail 47569 invoked by uid 500); 5 Oct 2010 17:57:03 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 47476 invoked by uid 500); 5 Oct 2010 17:57:02 -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 47464 invoked by uid 99); 5 Oct 2010 17:57:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Oct 2010 17:57:02 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Oct 2010 17:57:00 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o95HucYO021562 for ; Tue, 5 Oct 2010 17:56:38 GMT Message-ID: <22067146.552001286301398808.JavaMail.jira@thor> Date: Tue, 5 Oct 2010 13:56:38 -0400 (EDT) From: "Sanjay Radia (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-1073) Simpler model for Namenode's fs Image and edit Logs In-Reply-To: <1207504890.648331270171887350.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918088#action_12918088 ] Sanjay Radia commented on HDFS-1073: ------------------------------------ >> In order to do an offline fsck one can needs to dump the block map; ... >Sorry, can you elaborate a little bit here? ... This has nothing to do with Backup namenode. Currently the fsck is implemented inside the NN. We would like do this offiline. So one could do a dump of the block map and at the start of the dump record the transaction id. I believe that with this one would not have lock the FSNamspace. The above is just one use case of the transaction id. There are others. For example, during failover the transaction id would be useful for determining on one has the latest edits. > Simpler model for Namenode's fs Image and edit Logs > ---------------------------------------------------- > > Key: HDFS-1073 > URL: https://issues.apache.org/jira/browse/HDFS-1073 > Project: Hadoop HDFS > Issue Type: Improvement > Reporter: Sanjay Radia > Assignee: Todd Lipcon > Attachments: hdfs1073.pdf > > > The naming and handling of NN's fsImage and edit logs can be significantly improved resulting simpler and more robust code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.