hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5066) Inode tree with snapshot information visualization
Date Tue, 27 Aug 2013 07:05:53 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751032#comment-13751032
] 

Jing Zhao commented on HDFS-5066:
---------------------------------

bq. across different jvms

Not quite sure if I understand the requirement here. Do you mean we want to have a unique
id even over the time? In that case, I guess the current implementation, which depends on
an index number, cannot be unique either since we may have deleted some snapshots between
different client's visualization calls.

bq. each node need a unique label as node identifier

In general, I think we may want to traverse the graph only once here. And what we need is
some type of id for each inode which is unique in this traversing process. Thus the only challenge
here is to handle WithName nodes. In that case, to append WithName#lastSnapshotId may be our
best choice. And since this id is only for internal usage (not exposed in the final visualization),
I do not think "different encoding for different types" is a problem.
                
> 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

Mime
View raw message