You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2018/05/18 19:20:00 UTC
[jira] [Resolved] (AMBARI-23852) Provide a Framework For Adding A
Component During Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley resolved AMBARI-23852.
--------------------------------------
Resolution: Fixed
> Provide a Framework For Adding A Component During Upgrade
> ---------------------------------------------------------
>
> Key: AMBARI-23852
> URL: https://issues.apache.org/jira/browse/AMBARI-23852
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> During an upgrade it might be necessary to add a component automatically. For example, if a component is being replaced between stacks, then Ambari needs to remove the original component and add the new one.
> This is a new situation which we've never had before. AMBARI-23553 was created to automatically remove services/components during an upgrade which didn't appear in the new stack. However, to replace a service component is something that involves more thought.
> Perhaps we need an action that's similar to this:
> {code}
> <group xsi:type="cluster" name="ADD_YARN_TIMELINE_READER" title="Replace ATS with Timeline Reader">
> <execute-stage title="Replace ATS with Timeline Reader">
> <task xsi:type="add_component" service="YARN" component="TIMELINE_READER" host-service="YARN" host-component="APP_TIMELINE_SERVER">
> <summary>Add Timeline Reader to the cluster</summary>
> </task>
> </execute-stage>
> </group>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)