hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4343) When storageID of dfs.data.dir of being inconsistent, restart datanode will be failure.
Date Thu, 31 Jan 2013 00:21:12 GMT

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

Suresh Srinivas commented on HDFS-4343:
---------------------------------------

I took the liberty of editing the description. This is the expected behavior. Not sure what
is the bug/solution you are pointing to in this jira?
                
> When storageID of dfs.data.dir of being inconsistent, restart datanode will be failure.
> ---------------------------------------------------------------------------------------
>
>                 Key: HDFS-4343
>                 URL: https://issues.apache.org/jira/browse/HDFS-4343
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>         Environment: namenode datanode 
>            Reporter: liuyang
>         Attachments: hadoop-root-datanode-167-52-0-55.log, VERSION-1, VERSION-2
>
>
> A datanode has multiple storage directories configured using dfs.data.dir. When the storageID
in the VERSION files in these directories, the datanode fails to startup. Consider a scenario,
when old data in a storage directory is not cleared, the storage ID from it will not match
with storage ID of in other storage storage directories. In this situation, the DataNode will
quit and restart fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message