[
https://issues.apache.org/jira/browse/HADOOP-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688671#action_12688671
]
dhruba borthakur commented on HADOOP-5467:
------------------------------------------
> Over time, it is possible that this could serve as a tool to manually
> repair the fsimage.
> Definitely. The tool is written in such a way that it would be reasona
In that case, don't you want this tool to reside in a directory named something
like src/tools/org/apache/hadoop/tools/fsimage/.... The idea is that it can be
used to view the fsimage as well as modify it, etc.
regarding testing, maybe we can check in a few pre-created fsimage into the
test directory ( as a compressed tar file), the unit test could expand these
files, run the tool successfully (without any exceptions) on these images.
> 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: util
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Attachments: fsimage.xml, 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.
