[AMBARI-25240] Dynamically update Rolling Upgrade batch size

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: trunk, 2.6.2, 2.7.4
• Fix Version/s: trunk, 2.7.4
• Component/s: ambari-server
• Labels: pull-request-available
• Assignee: Viraj Jasani
• Reporter: Viraj Jasani
• Created: 11/Apr/19 19:40
• Updated: 31/May/19 16:51
• Resolved: 31/May/19 16:51

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.

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.

Issue Links

• links to: GitHub Pull Request #2926
• links to: GitHub Pull Request #2927
• links to: GitHub Pull Request #2928