Eric Yang created HDDS-1847:
-------------------------------
Summary: Datanode Kerberos principal and keytab config key looks
inconsistent
Key: HDDS-1847
URL: https://issues.apache.org/jira/browse/HDDS-1847
Project: Hadoop Distributed Data Store
Issue Type: Bug
Affects Versions: 0.5.0
Reporter: Eric Yang
Ozone Kerberos configuration can be very confusing:
| config name | Description |
| hdds.scm.kerberos.principal | SCM service principal |
| hdds.scm.kerberos.keytab.file | SCM service keytab file |
| ozone.om.kerberos.principal | Ozone Manager service principal |
| ozone.om.kerberos.keytab.file | Ozone Manager keytab file |
| hdds.scm.http.kerberos.principal | SCM service spnego principal |
| hdds.scm.http.kerberos.keytab.file | SCM service spnego keytab file |
| ozone.om.http.kerberos.principal | Ozone Manager spnego principal |
| ozone.om.http.kerberos.keytab.file | Ozone Manager spnego keytab file |
| hdds.datanode.http.kerberos.keytab | Datanode spnego keytab file |
| hdds.datanode.http.kerberos.principal | Datanode spnego principal |
| dfs.datanode.kerberos.principal | Datanode service principal |
| dfs.datanode.keytab.file | Datanode service keytab file |
The prefix are very different for each of the datanode configuration. It would
be nice to have some consistency for datanode.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
