[jira] [Commented] (AMBARI-21809) Pre-configure services during stack upgrade if Kerberos is enabled to reduce number of core service restarts when services are added

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-21809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150795#comment-16150795 ] 

Hadoop QA commented on AMBARI-21809:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12884961/AMBARI-21809_branch-2.6_02.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12137//console

This message is automatically generated.

> Pre-configure services during stack upgrade if Kerberos is enabled to reduce number of core service restarts when services are added
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21809
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21809
>             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-21809_branch-2.6_01.patch, AMBARI-21809_branch-2.6_02.patch, AMBARI-21809_trunk_01.patch, AMBARI-21809_trunk_02.patch
>
>
> Pre-configure (certain) services during a stack upgrade to HDP 2.6, when Kerberos is enabled, to reduce number of core service restarts when services are added.  
> Services to pre-configure include:
> * Knox
> * Beacon
> While upgrading the stack (EU or RU), processing the relevant Kerberos descriptor to find services marked to be _pre-configured_.  When a tagged service is encountered, process it if it is not installed. Apply only 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 upgrading the stack from HDP 2.5 to HDP 2.6.



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