ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-21602) Pre-configure services when Kerberos is enabled to reduce number of core service restarts when services are added
Date Fri, 06 Oct 2017 16:29:00 GMT

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

Robert Levas resolved AMBARI-21602.
-----------------------------------
    Resolution: Fixed

Committed to trunk
{noformat}
commit 01b79aae5553dcd89464d8f6558bdba031417a3f
Author: Robert Levas <rlevas@hortonworks.com>
Date:   Fri Oct 6 12:26:16 2017 -0400
{noformat}

Committed to branch-2.6
{noformat}
commit 154ff06fb1cdfe111c7dc023cc0009aa8ed5d888
Author: Robert Levas <rlevas@hortonworks.com>
Date:   Fri Oct 6 12:27:23 2017 -0400
{noformat}


> Pre-configure services when Kerberos is enabled to reduce number of core service restarts
when services are added
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21602
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21602
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.6.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21602_addendum_01.patch, AMBARI-21602_branch-2.6_01.patch,
AMBARI-21602_branch-2.6_02.patch, AMBARI-21602_trunk_01.patch, AMBARI-21602_trunk_02.patch
>
>
> Pre-configure (certain) services when Kerberos is enabled to reduce number of core service
restarts when services are added.  
> While processing the Kerberos descriptor, include services marked to be _pre-configured_.
 When a tagged service is encountered, process it weather it is installed or not. However
if it is not installed, only apply configuration changes for existing configuration types.
 This will set at least the core-site changes related to proxyuser and auth-to-local rules
properties. By doing this, if a tagged service is later installed, the settings will already
be in place in the existing service configs and thus the existing services will not need to
be restarted. 
> Caveats:
> * Default values for the uninstalled, tagged, services will be assumed 
> * The stack advisor will be used to suggest locations of components - used to build the
clusterHostInfo structure that may be used to derive property values. 
> Note: This processing is to occur when Kerberos is enabled. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message