[jira] [Updated] (HDFS-7120) When aborting NameNode or JournalNode due to metadata file problems, write the contents of the metadata directories and permissions to logs.
[ https://issues.apache.org/jira/browse/HDFS-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HDFS-7120: - Target Version/s: (was: 2.8.0) > 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: Sub-task > 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) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-7120) When aborting NameNode or JournalNode due to metadata file problems, write the contents of the metadata directories and permissions to logs.
[ https://issues.apache.org/jira/browse/HDFS-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated HDFS-7120: Issue Type: Sub-task (was: Improvement) Parent: HDFS-6185 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: Sub-task 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)
