[
https://issues.apache.org/jira/browse/HDFS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017081#comment-13017081
]
Jitendra Nath Pandey commented on HDFS-1813:
--------------------------------------------
Added a unit test for checking token in last block.
Unit test for READ access in getReplicaVisibleLength is difficult because this
method gets the access mode from the authenticated BlockTokenIdentifier. Since
security is disabled we can't get an authenticated identifier. However, we
already have tests to test if access modes are correctly set in the block
tokens.
> 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
>
>
> 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
