[ 
https://issues.apache.org/jira/browse/AMBARI-23127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383798#comment-16383798
 ] 

Hudson commented on AMBARI-23127:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #638 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/638/])
[AMBARI-23127] Allow default value of number of parallel tasks run (github: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5bc23e6c54a30d9584b3dc927a078aeaef0059e5])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) ambari-server/docs/configuration/index.md
* (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/ParallelScheduler.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
* (edit) pom.xml


> 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: 1h 10m
>  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)

Reply via email to