hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7120) When aborting NameNode or JournalNode due to metadata file problems, write the contents of the metadata directories and permissions to logs.
Date Mon, 22 Sep 2014 18:12:35 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143541#comment-14143541
] 

Chris Nauroth commented on HDFS-7120:
-------------------------------------

I was thinking it would be helpful to log something like ls output, with inclusion of permissions.
 {{MiniDFSCluster#createPermissionsDiagnosisString}} does something similar for tests already.

> When aborting NameNode or JournalNode due to metadata file problems, write the contents
of the metadata directories and permissions to logs.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7120
>                 URL: https://issues.apache.org/jira/browse/HDFS-7120
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: journal-node, namenode
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>
> If the NameNode or JournalNode aborts due to an unexpected error in the metadata directories,
often the root cause is that the metadata files are in an unexpected state, or permissions
are broken on the directories.  This issue proposes that during abort, we write additional
information about the directory state and permissions to the logs.  This can help speed up
diagnosis, and ultimately recovery.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message