[
https://issues.apache.org/jira/browse/HADOOP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628670#comment-14628670
]
Tsz Wo Nicholas Sze commented on HADOOP-692:
--------------------------------------------
Do you really need four or more levels? How about "/CoreDC-DC/rack/host"?
> Rack-aware Replica Placement
> ----------------------------
>
> Key: HADOOP-692
> URL: https://issues.apache.org/jira/browse/HADOOP-692
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 0.10.1
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.11.0
>
> Attachments: Rack_aware_HDFS_proposal.pdf, rack.patch
>
>
> This issue assumes that HDFS runs on a cluster of computers that spread
> across many racks. Communication between two nodes on different racks needs
> to go through switches. Bandwidth in/out of a rack may be less than the total
> bandwidth of machines in the rack. The purpose of rack-aware replica
> placement is to improve data reliability, availability, and network bandwidth
> utilization. The basic idea is that each data node determines to which rack
> it belongs at the startup time and notifies the name node of the rack id upon
> registration. The name node maintains a rackid-to-datanode map and tries to
> place replicas across racks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
