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

Andrew Purtell commented on HDFS-3672:
--------------------------------------

This can also be viewed as the query side of an API for device aware block 
placement. Consider renaming things like {{DiskBlockLocation}} to 
{{BlockDeviceLocation}} for such consideration. One attribute of 
{{BlockDeviceLocation}} should be {{enum Type}}. Then follow up work could be 
adding an API for specifying block placement according to 
{{BlockDeviceLocation.Type}}.

This would enable use cases like creating certain files on 
{{BlockDeviceLocation.Type.FLASH}} where they might be frequently accessed, 
especially for random reads; and others (and by default) on 
{{BlockDeviceLocation.Type.DISK}} for selecting spinning media.

Please pardon the interruption.
                
> Expose disk-location information for blocks to enable better scheduling
> -----------------------------------------------------------------------
>
>                 Key: HDFS-3672
>                 URL: https://issues.apache.org/jira/browse/HDFS-3672
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-alpha
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>         Attachments: hdfs-3672-1.patch, hdfs-3672-2.patch
>
>
> Currently, HDFS exposes on which datanodes a block resides, which allows 
> clients to make scheduling decisions for locality and load balancing. 
> Extending this to also expose on which disk on a datanode a block resides 
> would enable even better scheduling, on a per-disk rather than coarse 
> per-datanode basis.
> This API would likely look similar to Filesystem#getFileBlockLocations, but 
> also involve a series of RPCs to the responsible datanodes to determine disk 
> ids.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to