[
https://issues.apache.org/jira/browse/HDFS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017113#comment-13017113
]
Jitendra Nath Pandey commented on HDFS-1813:
--------------------------------------------
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
(version 1.3.9) warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec] +1 system test framework. The patch passed system test
framework compile.
> Hdfs Federation: Authentication using BlockToken in RPC to datanode fails.
> --------------------------------------------------------------------------
>
> Key: HDFS-1813
> URL: https://issues.apache.org/jira/browse/HDFS-1813
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Fix For: Federation Branch
>
> Attachments: HDFS-1813.1.patch, HDFS-1813.2.patch, HDFS-1813.3.patch
>
>
> Several issues are causing this problem
> 1. The last LocatedBlock returned by getBlockLocations doesn't have
> BlockToken.
> 2. The blockPoolTokenSecretManager is not initialized before created rpc
> server in datanode.
> 3. The getReplicaVisibleLength API in datanode expects WRITE permission in
> the block token, but the block tokens are generated with read permission only
> in getBlockLocations at namenode.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
