|
Description
|
Currently, when writing out a block, dfs will place one copy to a local data node, one copy to a rack local node
and another one to a remote node. This leads to a number of undesired properties:
1. The block will be rack-local to two tacks instead of three, reducing the advantage of rack locality based scheduling by 1/3.
2. The Blocks of a file (especiallya large file) are unevenly distributed over the nodes: One third will be on the local node, and two thirds on the nodes on the same rack. This may make some nodes full much faster than others,
increasing the need of rebalancing. Furthermore, this also make some nodes become "hot spots" if those big
files are popular and accessed by many applications.
|
Currently, when writing out a block, dfs will place one copy to a local data node, one copy to a rack local node
and another one to a remote node. This leads to a number of undesired properties:
1. The block will be rack-local to two tacks instead of three, reducing the advantage of rack locality based scheduling by 1/3.
2. The Blocks of a file (especiallya large file) are unevenly distributed over the nodes: One third will be on the local node, and two thirds on the nodes on the same rack. This may make some nodes full much faster than others,
increasing the need of rebalancing. Furthermore, this also make some nodes become "hot spots" if those big
files are popular and accessed by many applications.
|
|
Release Note
|
|
Change DFS block placement to allocate the first replica locally, the second off-rack, and the third intra-rack from the second.
|
Improvement
Closed
Major
DFS should place one replica per rack
