hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8244) HDFS Custom Storage Tier Policies
Date Fri, 24 Apr 2015 16:29:38 GMT

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

Arpit Agarwal updated HDFS-8244:
--------------------------------
    Description: 
Feature request to be able to define custom HDFS storage policies.

For example, being able to define DISK:2, Archive:n - 2.

Motivation for this is when integrating the archive tier on another cheaper storage system
such as Hedvig which we are not in control of and want to hedge our bets in case something
goes wrong with that archive storage system (it's new and unproven) we don't want just one
copy of the data left on our cluster in case we lose a node.

  was:
Feature request to be able to define custom HDFS storage policies.

For example, being able to define DISK:2, Archive:n - 2.

Motivation for this is when integrating the archive tier on another cheaper storage system
such as Hedvig which we are not in control of and want to hedge our bets in case something
goes wrong with that archive storage system (it's new and unproven) we don't want just one
copy of the data left on our cluster in case we lose a node.

Hari Sekhon
http://www.linkedin.com/in/harisekhon


> HDFS Custom Storage Tier Policies
> ---------------------------------
>
>                 Key: HDFS-8244
>                 URL: https://issues.apache.org/jira/browse/HDFS-8244
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: balancer & mover, datanode, HDFS, hdfs-client, namenode
>    Affects Versions: 2.6.0
>         Environment: HDP 2.2
>            Reporter: Hari Sekhon
>            Priority: Minor
>
> Feature request to be able to define custom HDFS storage policies.
> For example, being able to define DISK:2, Archive:n - 2.
> Motivation for this is when integrating the archive tier on another cheaper storage system
such as Hedvig which we are not in control of and want to hedge our bets in case something
goes wrong with that archive storage system (it's new and unproven) we don't want just one
copy of the data left on our cluster in case we lose a node.



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

Mime
View raw message