[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531648 ]
Hadoop QA commented on HADOOP-1914: ----------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12366866/namenodeProtocol3.patch against trunk revision r581047. @author +1. The patch does not contain any @author tags. javadoc +1. The javadoc tool did not generate any warning messages. javac +1. The applied patch does not generate any new compiler warnings. findbugs +1. The patch does not introduce any new Findbugs warnings. core tests +1. The patch passed core unit tests. contrib tests +1. The patch passed contrib unit tests. Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/860/testReport/ Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/860/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/860/artifact/trunk/build/test/checkstyle-errors.html Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/860/console This message is automatically generated. > 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, namenodeProtocol3.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.