Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
The NameNode and SecondaryNameNode have two different configuration knobs (dfs.namenode.kerberos.principal and dfs.secondary.namenode.kerberos.principal), but the secondary namenode fails authorization unless it is the same user.
Attachments
Issue Links
- duplicates
-
HDFS-2264 NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation
- Closed