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 121DFE43B for ; Thu, 24 Jan 2013 18:17:14 +0000 (UTC) Received: (qmail 12801 invoked by uid 500); 24 Jan 2013 18:17:13 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 12732 invoked by uid 500); 24 Jan 2013 18:17:13 -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 12705 invoked by uid 99); 24 Jan 2013 18:17:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2013 18:17:13 +0000 Date: Thu, 24 Jan 2013 18:17:13 +0000 (UTC) From: "Aaron T. Myers (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-4434) Provide a mapping from INodeId to INode 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-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561816#comment-13561816 ] Aaron T. Myers commented on HDFS-4434: -------------------------------------- I think Colin's point is that if the goal is to error out when a client's INode ID doesn't match what's in the NN's leases, then there's no need for a map from INode ID to INode. We need only note that the INode IDs don't match and throw an error. My understanding of the design/goals is based on [this comment|https://issues.apache.org/jira/browse/HDFS-4258?focusedCommentId=13537283&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13537283] made by Brandon. If the goals are more than this, I'd really like to see a little design doc for this work. > Provide a mapping from INodeId to INode > --------------------------------------- > > Key: HDFS-4434 > URL: https://issues.apache.org/jira/browse/HDFS-4434 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: namenode > Affects Versions: 3.0.0 > Reporter: Brandon Li > Assignee: Brandon Li > > This JIRA is to provide a way to access the INode via its id. The proposed solution is to have an in-memory mapping from INodeId to INode. -- 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