Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 94342104BB for ; Thu, 28 Nov 2013 14:32:53 +0000 (UTC) Received: (qmail 47471 invoked by uid 500); 28 Nov 2013 14:32:45 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 47401 invoked by uid 500); 28 Nov 2013 14:32:37 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 47379 invoked by uid 99); 28 Nov 2013 14:32:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Nov 2013 14:32:35 +0000 Date: Thu, 28 Nov 2013 14:32:35 +0000 (UTC) From: "Aleksandr Kovalenko (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-3915) Stop/Start components action in service configs not calculating correctly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Aleksandr Kovalenko created AMBARI-3915: ------------------------------------------- Summary: Stop/Start components action in service configs not calculating correctly Key: AMBARI-3915 URL: https://issues.apache.org/jira/browse/AMBARI-3915 Project: Ambari Issue Type: Task Components: client Affects Versions: 1.4.3 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 1.4.3 Attachments: AMBARI-3915.patch I had 2 config-groups which overrode the same config ({{yarn.nodemanager.log.retain-second}}). Now from the manage-config-groups dialog I removed the host from one config-group, and added it in the other config-group. Then I hit Save. YARN correctly said that 1 host needs restarts. I clicked on the 'Stop Components' button and it correctly stopped the NodeManager component. However the 'Start Components' button is not enabled. Refreshing etc. does not help either. -- This message was sent by Atlassian JIRA (v6.1#6144)