Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 10 Aug 2015 20:31:45 +0000 (UTC)
From: "Alejandro Fernandez (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12853954.1439238686000.24845.1439238705788@Atlassian.JIRA>
In-Reply-To: <JIRA.12853954.1439238686000@Atlassian.JIRA>
References: <JIRA.12853954.1439238686000@Atlassian.JIRA>
 <JIRA.12853954.1439238686642@arcas>
Subject: [jira] [Created] (AMBARI-12698) Update the stack by stopping and
 starting services in an orchestrated fashion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Alejandro Fernandez created AMBARI-12698:
--------------------------------------------

             Summary: 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
             Fix For: 2.2.0


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)