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 D524D1014A for ; Tue, 27 Aug 2013 03:55:07 +0000 (UTC) Received: (qmail 80537 invoked by uid 500); 27 Aug 2013 03:55:06 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 80465 invoked by uid 500); 27 Aug 2013 03:54:57 -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 80308 invoked by uid 99); 27 Aug 2013 03:54:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Aug 2013 03:54:54 +0000 Date: Tue, 27 Aug 2013 03:54:54 +0000 (UTC) From: "Binglin Chang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-5066) Inode tree with snapshot information visualization 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-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750939#comment-13750939 ] Binglin Chang commented on HDFS-5066: ------------------------------------- bq. Is it possible to remove the buildNodeSet method and the nodeset map, since inode Id, class name, and localName can all be identified from a given inode? I am afraid INodeId, className and localName can't provide uniqueness, many WithName can have same localName, I guess if we treat different class type with different encoding(WithCount_inodeid, WithName_inodeid_snapshotid, DstRef_inodeid), uniqueness is possible, but it looks a little strange. > Inode tree with snapshot information visualization > --------------------------------------------------- > > Key: HDFS-5066 > URL: https://issues.apache.org/jira/browse/HDFS-5066 > Project: Hadoop HDFS > Issue Type: Improvement > Reporter: Binglin Chang > Assignee: Binglin Chang > Priority: Minor > Attachments: HDFS-5066.v1.patch, visnap.png > > > It would be nice to be able to visualize snapshot information, in order to ease the understanding of related data structures. We can generate graph from in memory inode links. -- 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