Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 6 Dec 2012 11:53:12 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12618959.1354748255919.78.1354794792784@arcas>
In-Reply-To: <JIRA.12618959.1354748255919@arcas>
References: <JIRA.12618959.1354748255919@arcas>
Subject: [jira] [Commented] (HBASE-7285) HMaster fails to start with secure
 Hadoop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511295#comment-13511295 ] 

Hudson commented on HBASE-7285:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #285 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/285/])
    HBASE-7285 HMaster fails to start with secure Hadoop (Revision 1417690)

     Result = FAILURE
stack : 
Files : 
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java

                
> HMaster fails to start with secure Hadoop
> -----------------------------------------
>
>                 Key: HBASE-7285
>                 URL: https://issues.apache.org/jira/browse/HBASE-7285
>             Project: HBase
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 0.96.0
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>             Fix For: 0.96.0
>
>         Attachments: HBASE-7285.patch
>
>
> In current trunk, HMaster will fail to start with secure Hadoop if the user starting the process has not obtained a kerberos TGT.  The user starting the process should not be required to have a TGT, as the HMaster process self logs in using the configured keytab and principal.
> This is due to a log line in the HMaster constructor executing prior to the {{User.login()}} step:
> {code}
>     LOG.info("hbase.rootdir=" + FSUtils.getRootDir(this.conf) +
>         ", hbase.cluster.distributed=" + this.conf.getBoolean("hbase.cluster.distributed", false));
> {code}
> Here the FSUtils.getRootDir() winds up hitting the NameNode.  The fix is trivial, moving the log line to follow {{User.login()}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira