You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org> on 2011/04/07 19:04:05 UTC
[jira] [Updated] (HDFS-1813) Hdfs Federation: Authentication using
BlockToken in RPC to datanode fails.
[ https://issues.apache.org/jira/browse/HDFS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HDFS-1813:
---------------------------------------
Fix Version/s: Federation Branch
Summary: Hdfs Federation: Authentication using BlockToken in RPC to datanode fails. (was: Authentication using BlockToken in RPC to datanode fails.)
> 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
>
>
> 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