You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Simon Su (Jira)" <ji...@apache.org> on 2020/04/30 05:31:00 UTC
[jira] [Updated] (HDDS-3513) OzoneConfiguration missing
ozone-site.xml by default.
[ https://issues.apache.org/jira/browse/HDDS-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Su updated HDDS-3513:
---------------------------
Target Version/s: (was: 0.5.0)
> OzoneConfiguration missing ozone-site.xml by default.
> -----------------------------------------------------
>
> Key: HDDS-3513
> URL: https://issues.apache.org/jira/browse/HDDS-3513
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Simon Su
> Priority: Minor
> Fix For: 0.6.0
>
>
> OzoneConfiguration missing load ozone-site.xml by default, this may cause some issues when setup a secure ozone cluster.
> When we start a S3Gateway in secure mode (Kerberos), when start S3Gateway http server, it will use UserGroupInformation to check whether in security mode, which will load Configuration to check whether "hadoop.security.authentication" set to "KERBEROS". but unfortunately, default configuration will only load "core-site.xml, core-default.xml, hdfs-site.xml, hdfs-default.xml ozone-default.xml" and missing *{color:#ff0000}ozone-site.xml, {color} it*{color:#ff0000} {color:#172b4d}means we have to configure "hadoop.security.authentication" in one of default 5 config files if we want to start a secure S3Gateway.{color}{color}
> It's better to add ozone-site.xml into OzoneConfiguration by default, so we don't need to make one same configuration in different part.
--
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