hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6162) mapred hsadmin fails on a secure cluster
Date Fri, 14 Nov 2014 21:56:35 GMT

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

Jason Lowe updated MAPREDUCE-6162:
    Attachment: MAPREDUCE-6162v2.patch

New patch to fix a typo in the previous patch.  Manually tested on a secure cluster.

> 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
>         Attachments: MAPREDUCE-6162.patch, MAPREDUCE-6162v2.patch
> 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

View raw message