FAQ
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


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

Search Discussions

  • Jitendra Nath Pandey (JIRA) at Apr 7, 2011 at 8:10 pm
    [ https://issues.apache.org/jira/browse/HDFS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Jitendra Nath Pandey resolved HDFS-1813.
    ----------------------------------------

    Resolution: Fixed
    Hadoop Flags: [Reviewed]

    I have committed this to the branch.
    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
  • Jitendra Nath Pandey (JIRA) at Apr 8, 2011 at 2:46 am
    [ 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
  • Jitendra Nath Pandey (JIRA) at Apr 8, 2011 at 8:05 pm
    [ https://issues.apache.org/jira/browse/HDFS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Jitendra Nath Pandey resolved HDFS-1813.
    ----------------------------------------

    Resolution: Fixed

    Committed the latest patch.
    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, HDFS-1813.4.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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouphdfs-dev @
categorieshadoop
postedApr 7, '11 at 1:29a
activeApr 8, '11 at 8:05p
posts4
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Jitendra Nath Pandey (JIRA): 4 posts

People

Translate

site design / logo © 2022 Grokbase