hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Binglin Chang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5066) Inode tree with snapshot information visualization
Date Wed, 18 Sep 2013 14:39:55 GMT

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

Binglin Chang commented on HDFS-5066:

Thanks for the comments Jing Zhao, your concern makes sense.
I also hesitated to add new API in ClientProtocol, but for the running namenode service, there
is few interfaces can be used to invoke the visualization, another way is through web servlet
and add a config to only expose the servlet when config is enabled.
If we don't expose this tool, it can only be used in debugging unit test. 
I made this tool mostly for developers to understand snapshot internal and debugging, visualization
of millions files/directory does not seem possible and useful(it has way to much information).
So I think the options left are expose web servlet or just left it internal and used by tests.
What do you mean by "make the tool continue the visualization based on the last time result"?
Do you mean a dynamic visualization updates along with fs changes?

> 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, HDFS-5066.v2.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

View raw message