[MAPREDUCE-6162] mapred hsadmin fails on a secure cluster

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.7.0
• Component/s: jobhistoryserver
• Target Version/s: 2.7.0
• Hadoop Flags: Reviewed
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 14/Nov/14 16:42
• Updated: 10/Apr/15 20:19
• Resolved: 17/Nov/14 23:02

Description

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.