hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8361) Choose SSD over DISK in block placement
Date Tue, 16 Jun 2015 00:52:01 GMT

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

Tsz Wo Nicholas Sze updated HDFS-8361:
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.7.1
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks Joe and Jing for the reviewing.

I have committed this.

> Choose SSD over DISK in block placement
> ---------------------------------------
>
>                 Key: HDFS-8361
>                 URL: https://issues.apache.org/jira/browse/HDFS-8361
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>             Fix For: 2.7.1
>
>         Attachments: h8361_20150508.patch, h8361_20150612.patch
>
>
> BlockPlacementPolicyDefault chooses the StorageType by iterating the given StorageType
EnumMap in its natural order (the order in which the enum constants are declared).  So DISK
will be chosen over SSD in One-SSD policy since DISK is declared before SSD as shown below.
 We should choose SSD first.
> {code}
> public enum StorageType {
>   DISK(false),
>   SSD(false),
>   ARCHIVE(false),
>   RAM_DISK(true);
>   ...
> }
> {code}



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

Mime
View raw message