Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 14 Mar 2011 23:09:29 +0000 (UTC)
From: "Jitendra Nath Pandey (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1514528884.2381.1300144169708.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <62853775.2352.1300143930004.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (HDFS-1755) Hdfs Federation: The BPOfferService
 must always connect to namenode as the login user.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jitendra Nath Pandey updated HDFS-1755:
---------------------------------------

    Attachment: HDFS-1755.2.patch

The patch wraps the call to create namenode proxy within a getLoginUser().doAs block.

> 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
>
>
>   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