[
https://issues.apache.org/jira/browse/HDFS-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435310#comment-13435310
]
Suresh Srinivas commented on HDFS-3672:
---------------------------------------
bq. I put up some ramblings on HBASE-6572. The scope is much larger and there's
no timeline, it's a brainstorming issue. However, if you'd like this issue can
be linked to it.
Andrew, I am not sure how this jira, the solution it is providing helps
HBASE-6572. Some of the intent of HBASE-6572 is why I think the current
temporary hack is a wrong way to go about the solution. See my comments above
[here|https://issues.apache.org/jira/browse/HDFS-3672?focusedCommentId=13418911&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13418911]
and
[here|https://issues.apache.org/jira/browse/HDFS-3672?focusedCommentId=13431516&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13431516
]
> 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: design-doc-v1.pdf, design-doc-v2.pdf, hdfs-3672-1.patch,
> hdfs-3672-2.patch, hdfs-3672-3.patch, hdfs-3672-4.patch, hdfs-3672-5.patch,
> hdfs-3672-6.patch, hdfs-3672-7.patch, hdfs-3672-8.patch, hdfs-3672-9.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
