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

Posted to dev@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2015/10/27 15:53:27 UTC

[jira] [Updated] (AMBARI-13551) When adding components to a Kerberized cluster, the set of hosts to create principals for should be limited to only the relevant set

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

Robert Levas updated AMBARI-13551:
----------------------------------
    Attachment: AMBARI-13551_trunk_01.patch
                AMBARI-13551_branch-2.1_01.patch

> When adding components to a Kerberized cluster, the set of hosts to create principals for should be limited to only the relevant set
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13551
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13551
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.3
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: kerberos
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13551_branch-2.1_01.patch, AMBARI-13551_trunk_01.patch
>
>
> When adding components to a Kerberized cluster, the set of hosts to create principals for should be limited to only the relevant set.  This is because if a component for an existing service is added to an existing host, principals and keytab files for the existing components will get unnecessarily updated. 



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