Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 8 Apr 2011 02:46:05 +0000 (UTC)
From: "Jitendra Nath Pandey (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <723941415.42773.1302230765776.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2031094403.39530.1302139745831.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (HDFS-1813) Hdfs Federation: Authentication using
 BlockToken in RPC to datanode fails.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey reopened HDFS-1813:
----------------------------------------


Reverted the commit.

> 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