Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 4 Nov 2014 20:44:39 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12752632.1415080928000.414142.1415133879234@Atlassian.JIRA>
In-Reply-To: <JIRA.12752632.1415080928000@Atlassian.JIRA>
References: <JIRA.12752632.1415080928000@Atlassian.JIRA>
 <JIRA.12752632.1415080928921@arcas>
Subject: [jira] [Commented] (HDFS-7343) A comprehensive and flexible storage
 policy engine
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HDFS-7343:
--------------------------------------

Most of the ideas mentioned in the description of HDFS-4672 have made it in. Might be worth examining the remainder in the context of this issue. (Or not.)

> A comprehensive and flexible storage policy engine
> --------------------------------------------------
>
>                 Key: HDFS-7343
>                 URL: https://issues.apache.org/jira/browse/HDFS-7343
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Kai Zheng
>
> As discussed in HDFS-7285, it would be better to have a comprehensive and flexible storage policy engine considering file attributes, metadata, data temperature, storage type, EC codec, available hardware capabilities, user/application preference and etc.


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