hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9715) Check storage ID uniqueness on datanode startup
Date Tue, 02 Feb 2016 09:53:40 GMT

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

Vinayakumar B commented on HDFS-9715:

{{TestDFSRollback}} is failing because it expects, all data dirs to have same VERSION file,
but it will not after changing {{UpgradeUtilities.java}}.

So its better to exclude only {{storageId}} while comparing the props between VERSION files
across data dirs.

> Check storage ID uniqueness on datanode startup
> -----------------------------------------------
>                 Key: HDFS-9715
>                 URL: https://issues.apache.org/jira/browse/HDFS-9715
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 2.7.2
>            Reporter: Lei (Eddy) Xu
>            Assignee: Lei (Eddy) Xu
>         Attachments: HDFS-9715.00.patch, HDFS-9715.01.patch, HDFS-9715.02.patch
> We should fix this to check storage ID uniqueness on datanode startup. If someone has
manually edited the storage ID files, or if they have duplicated a directory (or re-added
an old disk) they could end up with a duplicate storage ID and not realize it. 
> The HDFS-7575 fix does generate storage UUID for each storage, but not checks the uniqueness
of these UUIDs.

This message was sent by Atlassian JIRA

View raw message