[jira] Commented: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

["dhruba borthakur (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528272 ] 

dhruba borthakur commented on HADOOP-1914:
------------------------------------------

It might be worthwhile to move two existing API: rollFsEdit and rollFsImage from the client protocol to the NameNode procotol. These two APIs are used by the Secondary Namenode to cause periodic checkpointing.

> 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
>
>
> 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.