You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/02 17:39:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17124124#comment-17124124 ]
Arpit Agarwal commented on HDDS-1354:
-------------------------------------
Is this a product issue or a test issue?
> 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: Marton Elek
> Assignee: Ajay Kumar
> Priority: Major
> Labels: regression-test
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org