[
https://issues.apache.org/jira/browse/AMBARI-25240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated AMBARI-25240:
----------------------------------
Fix Version/s: 2.7.4
2.6.2
trunk
Status: Patch Available (was: In Progress)
> Dynamically update Rolling Upgrade batch size
> ---------------------------------------------
>
> Key: AMBARI-25240
> URL: https://issues.apache.org/jira/browse/AMBARI-25240
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk, 2.6.2, 2.7.4
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Critical
> Labels: pull-request-available
> Fix For: trunk, 2.6.2, 2.7.4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We have a default value 100 for Rolling Upgrade batch size. In order to
> modify that size, upgrade.xml should have <max-degree-of-parallelism> or
> stack should define it.
> However, we can provide a way to update the batch size dynamically using some
> config that can be updated by client using Rest API and subsequent Rolling
> Upgrade can get the updated batch size from the config.
> Before starting off with Rolling Upgrade, we can update "cluster-env" config
> with property key: "max_degree_parallelism". If the value of this key is
> integer, that value will be selected as Batch Size. If not, then the default
> behavior will continue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
