[
https://issues.apache.org/jira/browse/HADOOP-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688223#action_12688223
]
dhruba borthakur commented on HADOOP-5467:
------------------------------------------
Awesome! This tool is cool.
>From the code, it appears that the tool parses the image file one record at a
>time instead of reading the entire file into memory. This is good, because
>this tool can run on a machine that has much less memory that the NameNode.
Is it possible to intelligently skip bad records? This will be useful in the
case when a system administrator is trying to fix a broken fsimage.
Over time, it is possible that this could serve as a tool to manually repair
the fsimage. If you envision that this is something for the future, then we
might want to name keep this tool in a directory named
src/tools/org/apache/hadoop/tools/fsimage/....
> 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
>
>
> 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.
