You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2014/11/14 18:00:39 UTC

[jira] [Updated] (MAPREDUCE-6162) mapred hsadmin fails on a secure cluster

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated MAPREDUCE-6162:
-----------------------------------------------
    Priority: Blocker  (was: Major)

> mapred hsadmin fails on a secure cluster
> ----------------------------------------
>
>                 Key: MAPREDUCE-6162
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6162
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 2.5.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Blocker
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)