hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HDFS-1755) Hdfs Federation: The BPOfferService must always connect to namenode as the login user.
Date Wed, 16 Mar 2011 22:26:29 GMT

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

Jitendra Nath Pandey resolved HDFS-1755.
----------------------------------------

      Resolution: Fixed
    Release Note: Committed to the branch.
    Hadoop Flags: [Reviewed]

> Hdfs Federation: The BPOfferService must always connect to namenode as the login user.
> --------------------------------------------------------------------------------------
>
>                 Key: HDFS-1755
>                 URL: https://issues.apache.org/jira/browse/HDFS-1755
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: Federation Branch
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: Federation Branch
>
>         Attachments: HDFS-1755.2.patch, HDFS-1755.3.patch
>
>
>   The BPOfferService thread when started, normally connects to the namenode as the login
user. But in case of refreshNamenodes a new BPOfferService may be started in the context of
an rpc call where the user is dfsadmin. In such a case the connection to the namenode will
fail. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message