You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org> on 2011/04/07 03:29:05 UTC

[jira] [Created] (HDFS-1813) Authentication using BlockToken in RPC to datanode fails.

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

[jira] [Reopened] (HDFS-1813) Hdfs Federation: Authentication using BlockToken in RPC to datanode fails.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ 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

[jira] [Resolved] (HDFS-1813) Hdfs Federation: Authentication using BlockToken in RPC to datanode fails.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ 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

[jira] [Resolved] (HDFS-1813) Hdfs Federation: Authentication using BlockToken in RPC to datanode fails.

Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
     [ 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