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

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.0
• Component/s: ambari-server
• Assignee: Robert Levas
• Reporter: Robert Levas
• Due: 31/Aug/17
• Created: 24/Aug/17 21:21
• Updated: 01/Sep/17 17:42
• Resolved: 01/Sep/17 16:59

Description

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.

Issue Links

• is related to: AMBARI-21602 Pre-configure services when Kerberos is enabled to reduce number of core service restarts when services are added
• links to: ReviewBoard