[
https://issues.apache.org/jira/browse/AMBARI-21602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130243#comment-16130243
]
Hadoop QA commented on AMBARI-21602:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12882231/AMBARI-21602_trunk_01.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 10 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12008//console
This message is automatically generated.
> 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_branch-2.6_01.patch,
> AMBARI-21602_trunk_01.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)
