Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 19 Sep 2013 19:49:54 +0000 (UTC)
From: "Arpit Agarwal (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12669525.1379620077257.163961.1379620194119@arcas>
In-Reply-To: <JIRA.12669525.1379620077257@arcas>
References: <JIRA.12669525.1379620077257@arcas>
Subject: [jira] [Created] (HDFS-5232) Protocol changes to transmit
 StorageUuid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Arpit Agarwal created HDFS-5232:
-----------------------------------

             Summary: Protocol changes to transmit StorageUuid
                 Key: HDFS-5232
                 URL: https://issues.apache.org/jira/browse/HDFS-5232
             Project: Hadoop HDFS
          Issue Type: Sub-task
          Components: datanode, hdfs-client, namenode
    Affects Versions: Heterogeneous Storage (HDFS-2832)
            Reporter: Arpit Agarwal
            Assignee: Arpit Agarwal


Currently the StorageID is used to identify both the Datanode and the storage. This works because we treat all storages attached to the Datanode as a single storage unit.

We plan to replace the StorageID with two independent IDs:
# Datanode UUID - this will be a string that uniquely identifies each Datanode in the cluster. For upgraded clusters, the Datanode UUID will be the StorageID prior to the upgrade.
# Storage UUID - Each storage attached to the datanode will be identified by a UUID.

--
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