-
Type:
Bug
-
Status: Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 2.5.0
-
Fix Version/s: 2.7.0
-
Component/s: jobhistoryserver
-
Labels:None
-
Target Version/s:
-
Hadoop Flags:Reviewed
Attempts to use mapred hsadmin fail on a secure cluster for a couple of reasons. The HSAdmin client isn't configuring the principal config key for the protocol, resulting in a "Failed to specify server's Kerberos principal name" error. The principal can be specified manually on the command-line via -Dhadoop.security.service.user.name.key, but then it results in a "Protocol interface ... is not known" error because HSAdminServer is not registering an appropriately configured policy provider when authorization is enabled.