You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2012/12/05 23:57:57 UTC
[jira] [Created] (HBASE-7285) HMaster fails to start with secure
Hadoop
Gary Helmling created HBASE-7285:
------------------------------------
Summary: 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
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
[jira] [Commented] (HBASE-7285) HMaster fails to start with secure
Hadoop
Posted by "Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510881#comment-13510881 ]
Ted Yu commented on HBASE-7285:
-------------------------------
+1 on patch.
> 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
> 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
[jira] [Updated] (HBASE-7285) HMaster fails to start with secure
Hadoop
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Helmling updated HBASE-7285:
---------------------------------
Attachment: HBASE-7285.patch
Patch moving the log line to follow the login step.
> 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
> 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
[jira] [Commented] (HBASE-7285) HMaster fails to start with secure
Hadoop
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510926#comment-13510926 ]
Gary Helmling commented on HBASE-7285:
--------------------------------------
Thanks for quick review guys!
> 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
[jira] [Resolved] (HBASE-7285) HMaster fails to start with secure
Hadoop
Posted by "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
[jira] [Commented] (HBASE-7285) HMaster fails to start with secure
Hadoop
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511066#comment-13511066 ]
Hudson commented on HBASE-7285:
-------------------------------
Integrated in HBase-TRUNK #3594 (See [https://builds.apache.org/job/HBase-TRUNK/3594/])
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