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] [Updated] (HDFS-5066) Inode tree with snapshot information visualization
Date Wed, 28 Aug 2013 13:58:53 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Binglin Chang updated HDFS-5066:
--------------------------------

    Attachment: HDFS-5066.v2.patch

New patch addressing previous comments, changes:
1. unique id is formatted as:
   simpleClassName_inodeid_lastsnapshot WithName
   simpleClassName_inodeid Other

2. Previous buildNodeset use DFS to traverse the graph, which is problematic if depth constrain
is used, so it is changed to BFS.

3. Add subgraph max node number constrain(500) to prevent abuse.   

3. I tried to finish select subgraph and graph generation in one traversal, but latter I found
it impossible, it is a direct graph rather than a tree, we can not know whether an edge belong
to this subgraph or not before we actually build the subgraph first. So the current solution
traverse the graph to build subgraph first and keep all subgraph nodes in a map, then iterate
over the map(json format has changed to adapt this change). 

                
> 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

Mime
View raw message