[ 
https://issues.apache.org/jira/browse/HDDS-1847?focusedWorklogId=336990&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-336990
 ]

ASF GitHub Bot logged work on HDDS-1847:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/Oct/19 18:32
            Start Date: 31/Oct/19 18:32
    Worklog Time Spent: 10m 
      Work Description: anuengineer commented on issue #1678: HDDS-1847: 
Datanode Kerberos principal and keytab config key looks inconsistent
URL: https://github.com/apache/hadoop/pull/1678#issuecomment-548510969
 
 
   I have committed this patch into hadoop-ozone branch. Not apache:trunk. 
   
   Here is the commit info. 
   
   commit 8527a9d9ceb0e1b2ba3bfc8ebc06e7589135f7f3 (HEAD -> master, 
origin/master, origin/HEAD)
   Author: Anu Engineer <aengin...@apache.org>
   Date:   Thu Oct 31 11:19:54 2019 -0700
   
       HDDS-1847: Datanode Kerberos principal and keytab config key looks 
inconsistent
       Contributed by christeoh.
   
   
   @christeoh  Thank you for the contribution. @macroadster  Thanks for 
comments and filing the JIRA.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 336990)
    Time Spent: 1h  (was: 50m)

> 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
>            Assignee: Chris Teoh
>            Priority: Major
>              Labels: newbie, pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to