You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Viraj Jasani (JIRA)" <ji...@apache.org> on 2019/04/11 19:41:00 UTC
[jira] [Updated] (AMBARI-25240) Dynamically update Rolling Upgrade
batch size
[ https://issues.apache.org/jira/browse/AMBARI-25240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani updated AMBARI-25240:
----------------------------------
Description:
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.
was:
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.
> Dynamically update Rolling Upgrade batch size
> ---------------------------------------------
>
> Key: AMBARI-25240
> URL: https://issues.apache.org/jira/browse/AMBARI-25240
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: trunk, 2.6.2, 2.7.4
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Critical
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)