[jira] [Commented] (AMBARI-25244) Rolling Upgrade support for rack based hosts

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on AMBARI-25244:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10497 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10497/])
[AMBARI-25244] : Rack based parallel restart for Rolling Upgrade (#2996) (amagyar: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=99b2bee07a6359857a6e03396d2884425f57f6f0])
* (edit) ambari-server/pom.xml
* (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/upgrade/orchestrate/UpgradeHelperTest.java
* (add) ambari-server/src/examples/rack_hosts.yaml
* (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/upgrade/Grouping.java


> 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
>          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)