Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <444153770.1239387314852.JavaMail.jira@brutus>
Date: Fri, 10 Apr 2009 11:15:14 -0700 (PDT)
From: "Jakob Homan (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5467) Create an offline fsimage image
 viewer
In-Reply-To: <1480368157.1236819711193.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697897#action_12697897 ] 

Jakob Homan commented on HADOOP-5467:
-------------------------------------

The test failed because Hudson doesn't know about the two binaries  
files that need to be added.  I guess it will have to be tested  
manually by the reviewer after adding the two fsimage files.


> Create an offline fsimage image viewer
> --------------------------------------
>
>                 Key: HADOOP-5467
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5467
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>         Attachments: fsimage.xml, fsimageV18, fsimageV19, HADOOP-5467.patch, HADOOP-5467.patch, HADOOP-5467.patch, HADOOP-5467.patch, HADOOP-5467.patch
>
>
> It would be useful to have a tool to examine/dump the contents of the fsimage file to human-readable form.  This would allow analysis of the namespace (file usage, block sizes, etc) without impacting the operation of the namenode.  XML would be reasonable output format, as it can be easily viewed, compressed and manipulated via either XSLT or XQuery.  
> I've started work on this and will have an initial version soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.