|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Issue Links:
|
Dependants
|
|
|
|
This issue blocks:
|
|
HADOOP-1652
Rebalance data blocks when new data nodes added or data nodes become full
|
|
|
|
|
|
|
| Resolution Date: |
02/Oct/07 06:43 PM
|
|
For the security purpose, it is nice to have a NamenodeProtocol to allow secondary namenodes and rebalacing processes to communicate with a primary namenode. In the first version the NamenodeProtocol is going to support one RPC:
BlockLocations[] getBlocks(DatanodeID datanode, long size);
This RPC allows a rebalancing process to fetch a partial blocks map from a namenode. It returns a list of blocks on the given datanode and its locations, whose total size is the given size.
|
|
Description
|
For the security purpose, it is nice to have a NamenodeProtocol to allow secondary namenodes and rebalacing processes to communicate with a primary namenode. In the first version the NamenodeProtocol is going to support one RPC:
BlockLocations[] getBlocks(DatanodeID datanode, long size);
This RPC allows a rebalancing process to fetch a partial blocks map from a namenode. It returns a list of blocks on the given datanode and its locations, whose total size is the given size. |
Show » |
| No work has yet been logged on this issue.
|
|
New Feature
HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode
