[
https://issues.apache.org/jira/browse/AMBARI-25244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated AMBARI-25244:
----------------------------------
Fix Version/s: 2.7.4
trunk
Status: Patch Available (was: In Progress)
> 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: 3h 40m
> 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)
