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

Todd Lipcon commented on HDFS-2832:
-----------------------------------

Just read through the design doc. Thanks for writing it up.

One thing I noticed under tooling that is not covered is extensions to the "fs 
-du" and/or "fs -count" command. Given that SSD is typically a very constrained 
resource, I imagine that administrators will want to be able to see where the 
space usage is going on a directory hierarchy level, in order to chase down 
users who are using too much (or applications which accidentally are specifying 
all their files should be on SSD).

Similarly, what's the planned way in which existing FsShell commands that write 
data will be extended to specify these policies? For example, if I want to 
upload a file with "hadoop fs -put", how can I specify that it should go on SSD?

Maybe I missed it, but are there other CLI extensions planned in order to 
retrieve and set the file attributes necessary to migrate data?
                
> Enable support for heterogeneous storages in HDFS
> -------------------------------------------------
>
>                 Key: HDFS-2832
>                 URL: https://issues.apache.org/jira/browse/HDFS-2832
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>    Affects Versions: 0.24.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: 20130813-HeterogeneousStorage.pdf
>
>
> HDFS currently supports configuration where storages are a list of 
> directories. Typically each of these directories correspond to a volume with 
> its own file system. All these directories are homogeneous and therefore 
> identified as a single storage at the namenode. I propose, change to the 
> current model where Datanode * is a * storage, to Datanode * is a collection 
> * of strorages. 

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

Reply via email to