[
https://issues.apache.org/jira/browse/AMBARI-23127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382937#comment-16382937
]
Hudson commented on AMBARI-23127:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8794 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8794/])
[AMBARI-23127] Allow default value of number of parallel tasks run (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=7345490d8992da2e8ae0ea7efcc654d4d6dac15d])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) ambari-server/docs/configuration/index.md
* (edit) pom.xml
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ParallelScheduler.java
> Allow default value of number of parallel tasks run during Upgrade to be
> customizable
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-23127
> URL: https://issues.apache.org/jira/browse/AMBARI-23127
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> On large clusters of 1000+ nodes the default value of 100 for max degree of
> parallelism results in Stop and Start command batches of 100 hosts and
> resulting operation taking longer because of the default batch size. This
> Jira adds a possible override through ambari.properties.
> Property:
> {noformat}
> stack.upgrade.default.parallelism{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)