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

Alejandro Fernandez updated AMBARI-14076:
-----------------------------------------
    Description: 
We have a limitation today in the Upgrade Packs used for NonRolling (Express) 
Upgrade in which the ExecteStage class can only have a single Task, and this 
results in a lot of repetition and verbose packs.

E.g.,
{code}
      <!--HBASE-->
      <execute-stage service="HBASE" component="HBASE_MASTER" title="Apply 
config changes for HBase Master">
        <task xsi:type="configure" 
id="hdp_2_3_0_0_hbase_master_set_global_memstore_size"/>
      </execute-stage>

      <execute-stage service="HBASE" component="HBASE_MASTER" 
title="Calculating HBase Properties">
        <task xsi:type="server_action" summary="Calculating HBase Properties" 
class="org.apache.ambari.server.serveraction.upgrades.HBaseConfigCalculation" />
      </execute-stage>

      <execute-stage service="HBASE" component="HBASE_MASTER" title="Apply 
config changes for HBase Master">
        <task xsi:type="configure" 
id="hdp_2_3_0_0_hbase_master_adjust_authorization_coprocessors"/>
      </execute-stage>
{code}

Instead, a single ExecuteStage should have all of the tasks.
The ExecuteStage class is inside ClusterGrouping.java

  was:
We have a limitation today in the Upgrade Packs used for NonRolling (Express) 
Upgrade in which the ExecteStage class can only have a single Task, and this 
results in a lot of repetition and verbose packs.

E.g.,
{code}
      <!--HBASE-->
      <execute-stage service="HBASE" component="HBASE_MASTER" title="Apply 
config changes for HBase Master">
        <task xsi:type="configure" 
id="hdp_2_3_0_0_hbase_master_set_global_memstore_size"/>
      </execute-stage>

      <execute-stage service="HBASE" component="HBASE_MASTER" 
title="Calculating HBase Properties">
        <task xsi:type="server_action" summary="Calculating HBase Properties" 
class="org.apache.ambari.server.serveraction.upgrades.HBaseConfigCalculation" />
      </execute-stage>

      <execute-stage service="HBASE" component="HBASE_MASTER" title="Apply 
config changes for HBase Master">
        <task xsi:type="configure" 
id="hdp_2_3_0_0_hbase_master_adjust_authorization_coprocessors"/>
      </execute-stage>
{code}

The ExecuteStage class is inside ClusterGrouping.java


> Stack Upgrade: ExecuteStage class to support a list of Tasks as opposed to a 
> single one
> ---------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14076
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14076
>             Project: Ambari
>          Issue Type: Story
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.2.0
>
>
> We have a limitation today in the Upgrade Packs used for NonRolling (Express) 
> Upgrade in which the ExecteStage class can only have a single Task, and this 
> results in a lot of repetition and verbose packs.
> E.g.,
> {code}
>       <!--HBASE-->
>       <execute-stage service="HBASE" component="HBASE_MASTER" title="Apply 
> config changes for HBase Master">
>         <task xsi:type="configure" 
> id="hdp_2_3_0_0_hbase_master_set_global_memstore_size"/>
>       </execute-stage>
>       <execute-stage service="HBASE" component="HBASE_MASTER" 
> title="Calculating HBase Properties">
>         <task xsi:type="server_action" summary="Calculating HBase Properties" 
> class="org.apache.ambari.server.serveraction.upgrades.HBaseConfigCalculation" 
> />
>       </execute-stage>
>       <execute-stage service="HBASE" component="HBASE_MASTER" title="Apply 
> config changes for HBase Master">
>         <task xsi:type="configure" 
> id="hdp_2_3_0_0_hbase_master_adjust_authorization_coprocessors"/>
>       </execute-stage>
> {code}
> Instead, a single ExecuteStage should have all of the tasks.
> The ExecuteStage class is inside ClusterGrouping.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to