You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2007/10/01 21:19:50 UTC
[jira] Updated: (HADOOP-1914) HDFS should have a NamenodeProtocol
to allow secondary namenodes and rebalancing processes to communicate with
a primary namenode
[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hairong Kuang updated HADOOP-1914:
----------------------------------
Status: Open (was: Patch Available)
> HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-1914
> URL: https://issues.apache.org/jira/browse/HADOOP-1914
> Project: Hadoop
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.14.1
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.15.0
>
> Attachments: namenodeProtocol.patch, namenodeProtocol1.patch, namenodeProtocol2.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.