hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7647) DatanodeManager.sortLocatedBlocks() sorts DatanodeIDs but not StorageIDs
Date Wed, 21 Jan 2015 18:26:35 GMT

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

Konstantin Shvachko commented on HDFS-7647:
-------------------------------------------

Yes, I would go with simple. That is, sort DatanodeIDs, then use the mapping to reorganize
storages. The mapping of course could be an index array as Arpit suggested.

> DatanodeManager.sortLocatedBlocks() sorts DatanodeIDs but not StorageIDs
> ------------------------------------------------------------------------
>
>                 Key: HDFS-7647
>                 URL: https://issues.apache.org/jira/browse/HDFS-7647
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Milan Desai
>            Assignee: Milan Desai
>
> DatanodeManager.sortLocatedBlocks() sorts the array of DatanodeIDs inside each LocatedBlock,
but does not touch the array of StorageIDs and StorageTypes. As a result, the DatanodeIDs
and StorageIDs/StorageTypes are mismatched. The method is called by FSNamesystem.getBlockLocations(),
so the client will not know which StorageID/Type corresponds to which DatanodeID.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message