[ 
https://issues.apache.org/jira/browse/HDFS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suresh Srinivas updated HDFS-4343:
----------------------------------

    Description: 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.  (was: The dfs.data.dir is configured 
multi-directories, When the storageID of one directory is different from other 
directoried, restore datanode is fail.
Consider this scene, when the history data is not clear, DataNode will read the 
VERSION of the history data, But the VERSION is different from the other new 
data. In this situation, the DataNode will be quit and restart fail.)
    
> 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

Reply via email to