[jira] [Updated] (AMBARI-7794) Setting hadoop.security.authorization=true in a non-Kerberized cluster causes DataNodes to not start

["Jaimin D Jetly (JIRA)" <ji...@apache.org>]

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

Jaimin D Jetly updated AMBARI-7794:
-----------------------------------
    Attachment: AMBARI-7794.patch

> Setting hadoop.security.authorization=true in a non-Kerberized cluster causes DataNodes to not start
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-7794
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7794
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.6.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7794.patch
>
>
> This side effect (hadoop.security.authorization=true breaking things when hadoop.security.authentication=simple) was introduced in Ambari-1.6.0 via AMBARI-5387; this release coincided with Blueprints feature, but the problem happens with non-BP deployed cluster as well.
> We should fix the stack definition so that principals and keytabs properties are not defined when the cluster is not Kerberized.



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