You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Xiaoyu Yao (JIRA)" <ji...@apache.org> on 2019/04/02 21:04:02 UTC
[jira] [Updated] (HDDS-1354) Kerberos principal configuration of
OzoneManager doesn't use FQDN
[ https://issues.apache.org/jira/browse/HDDS-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoyu Yao updated HDDS-1354:
-----------------------------
Target Version/s: 0.5.0 (was: 0.4.0)
> Kerberos principal configuration of OzoneManager doesn't use FQDN
> -----------------------------------------------------------------
>
> Key: HDDS-1354
> URL: https://issues.apache.org/jira/browse/HDDS-1354
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Elek, Marton
> Assignee: Ajay Kumar
> Priority: Major
>
> In the "*.kerberos.principal" settings hadoop supports the _HOST variable which is replaced to the fully qualified domain name.
> For example:
> {code}
> OZONE-SITE.XML_hdds.scm.kerberos.principal: "scm/_HOST@EXAMPLE.COM"
> {code}
> It works well with scm but for om it uses the hostname instead of the FQDN. (SCM uses the HddsServerUtil.getScmBlockClientBindAddress which uses the _bind_ address but the om uses the om rpc address).
> I would suggest to use the same behaviour for both SCM and OM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org