[jira] [Resolved] (HBASE-7285) HMaster fails to start with secure Hadoop

["stack (JIRA)" <ji...@apache.org>]

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

stack resolved HBASE-7285.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.96.0
         Assignee: Gary Helmling
     Hadoop Flags: Reviewed

Thanks Gary.  I think that log line was my bright idea.  Committed to trunk (Problem is not in 0.94).
                
> 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