[
https://issues.apache.org/jira/browse/AMBARI-25244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858700#comment-16858700
]
Hudson commented on AMBARI-25244:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #517 (See
[https://builds.apache.org/job/Ambari-branch-2.7/517/])
[AMBARI-25244] : Rack based parallel restart for Rolling Upgrade (amagyar:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=146ede00d696c3f9afc2e203845d327e9a8057f6])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
* (edit) ambari-server/pom.xml
* (add) ambari-server/src/examples/rack_hosts.yaml
> Rolling Upgrade support for rack based hosts
> --------------------------------------------
>
> Key: AMBARI-25244
> URL: https://issues.apache.org/jira/browse/AMBARI-25244
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: trunk, 2.7.4
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Critical
> Labels: pull-request-available
> Fix For: trunk, 2.7.4
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> Ambari managed Rolling Upgrade has batch size concept with which multiple
> hosts are upgraded in parallel. e.g. slave/client components are restarted on
> multiple hosts in parallel.
> However, we should provide support for parallel hosts upgrade that exist on
> single rack. If client provides location of rack to hosts mapping file
> location as part of cluster-env property, we should read the mapping and
> proceed with parallel Rolling Restart on multiple hosts on single rack.
> This can significantly improve resiliency and availability as slave/client
> components that don't belong to single rack won't be restarted in parallel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
