You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Jaimin D Jetly (JIRA)" <ji...@apache.org> on 2014/10/15 19:34:35 UTC

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

Jaimin D Jetly created AMBARI-7794:
--------------------------------------

             Summary: 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


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)