hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-11139) Ozone: SCM: Handle duplicate Datanode ID
Date Wed, 23 May 2018 03:01:00 GMT

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

Anu Engineer resolved HDFS-11139.
    Resolution: Won't Fix

> Ozone: SCM: Handle duplicate Datanode ID 
> -----------------------------------------
>                 Key: HDFS-11139
>                 URL: https://issues.apache.org/jira/browse/HDFS-11139
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>    Affects Versions: HDFS-7240
>            Reporter: Anu Engineer
>            Assignee: Anu Engineer
>            Priority: Major
>              Labels: OzonePostMerge, tocheck
>             Fix For: HDFS-7240
> The Datanode ID is used when a data node registers. It is assumed that datanodes are
unique across the cluster. 
> However due to operator error or other cases we might encounter duplicate datanode ID.
SCM should be able to recognize this and handle in correctly. Here is a sub-set  of datanode
scenarios it needs to handle.
> 1. Normal Datanode
> 2.  Copy of a Datanode metadata by operator to another node
> 3. A Datanode being renamed - hostname change
> 4. Container Reports -- 2 machines with same datanode ID. SCM thinks they are same node.
> 5. Decommission --  we decommission both nodes if IDs are same.
> 6. Commands will be send to both nodes.
> So it is necessary that SCM identity when a datanode is reusing a datanode ID that is
already used by another node.  

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

View raw message