hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1133) Tools to analyze and debug namenode on a production cluster
Date Fri, 23 Mar 2007 21:27:32 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483759

dhruba borthakur commented on HADOOP-1133:

Hi Raghu, thanks for your comments. I am printing the datanodes in the log because I am looking
at this as a support tool and would liekto capture as much data as possible in the log. I
can then ask a cluster administrator to run this tool and i will have everything I need to
analyze the cluster. I would hate to ask the cluster admin to run multiple commands to generate
the info I need.

Regarding the locking question: you are right that we might be a getting a consistent picture
of all the data structures that are being dumped. But each structure is locked individually,
this should avoid causing any exceptions.

> Tools to analyze and debug namenode on a production cluster
> -----------------------------------------------------------
>                 Key: HADOOP-1133
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1133
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: dhruba borthakur
>         Assigned To: dhruba borthakur
>         Attachments: metasave.patch
> I would like to have a tool that dumps namenode data structures to a log file. This is
especially useful in debugging a production cluster where attaching a debugger to the namenode
is not a feasible option.

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

View raw message