ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-12698) Update the stack by stopping and starting services in an orchestrated fashion
Date Sat, 15 Aug 2015 00:03:45 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-12698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Fernandez updated AMBARI-12698:
-----------------------------------------
    Labels: branch-dev-stop-all-upgrade  (was: )

> Update the stack by stopping and starting services in an orchestrated fashion
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-12698
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12698
>             Project: Ambari
>          Issue Type: Epic
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Critical
>              Labels: branch:branch-dev-stop-all-upgrade
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-12698_design_review.docx, AMBARI-12698_design_review.pdf
>
>
> Ambari needs to provide an option to upgrade the stack that is much faster, by taking
downtime. Instead of rolling restarts, this will stop all services, and start them one at
a time, with all hosts starting in parallel/batches.
> Benefits:
> * Relaxes requirements since NameNode HA is not needed
> * Faster since,
> ** Can upgrade an entire component by parallelizing across hosts. E.g., all ZK servers
at once
> ** Parallelize across components. E.g., Falcon Server and Storm Nimbus servers in parallel



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message