Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 4 Jul 2016 14:50:11 +0000 (UTC)
From: "Dmytro Sen (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12986617.1467643796000.19539.1467643811217@Atlassian.JIRA>
In-Reply-To: <JIRA.12986617.1467643796000@Atlassian.JIRA>
References: <JIRA.12986617.1467643796000@Atlassian.JIRA> <JIRA.12986617.1467643796580@arcas>
Subject: [jira] [Created] (AMBARI-17552) 'Restart all' services fails due to
 dependency on other service components
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 04 Jul 2016 14:50:14 -0000

Dmytro Sen created AMBARI-17552:
-----------------------------------

             Summary: 'Restart all' services fails due to dependency on other service components
                 Key: AMBARI-17552
                 URL: https://issues.apache.org/jira/browse/AMBARI-17552
             Project: Ambari
          Issue Type: Bug
          Components: stacks
    Affects Versions: 2.4.0
            Reporter: Dmytro Sen
            Assignee: Dmytro Sen
            Priority: Critical
             Fix For: 2.4.0


Looks like we have a dependency mechanism in place due to which the newly added "Restart all Services" operation does not work as expected in some cases
Here is my scenario:
1. Deploy a cluster (HDP-2.4.2.0) with core services (HDFS, YARN, ZK, MR) and Ambari-2.4.0.0 (ambari-server-2.4.0.0-680.x86_64)
2. Add Spark, Hive, Tez, Pig to the cluster and let it finish
3. At the end of service addition, there is an icon against HDFS, YARN, MR indicating these three services need restart
4. Try 'Restart all Required' operation
Result:
Failures at ATS start, which aborts the whole restart operation.


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