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 9D5C717BB0 for ; Mon, 13 Oct 2014 17:11:34 +0000 (UTC) Received: (qmail 72312 invoked by uid 500); 13 Oct 2014 17:11:34 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 72266 invoked by uid 500); 13 Oct 2014 17:11:34 -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 72047 invoked by uid 99); 13 Oct 2014 17:11:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Oct 2014 17:11:34 +0000 Date: Mon, 13 Oct 2014 17:11:33 +0000 (UTC) From: "Dmitry Lysnichenko (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-7761) stale_configs parameter works incorrectly for Flume MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-7761: --------------------------------------- Attachment: AMBARI-7761_branch-1.7.0.patch AMBARI-7761.patch > stale_configs parameter works incorrectly for Flume > --------------------------------------------------- > > Key: AMBARI-7761 > URL: https://issues.apache.org/jira/browse/AMBARI-7761 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 1.7.0 > Environment: 3-node CentOS 6.4 > HDP 2.1 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > Fix For: 1.7.0 > > Attachments: AMBARI-7761.patch, AMBARI-7761_branch-1.7.0.patch > > > *STR:* > # Deployed cluster with Flume but without Flume Agents > # Added Flume agent component on each host. > # Crated config groups for Flume: _group1_(assigned host _c6401_) and _group2_(assigned host _c6402_). Note that host _c6403_ is in _Flume Default_ group. > # Overrided flume.conf for _group1_ and _group2_ with custom values. > # Restarted all components for Flume (there are no restart indicators after restart). > # Setted flume.conf for _Flume Default_ group with custom value. (_Flume Default_ had only c6403). > # Clicked 'Save'. > *Result:* Appeared restart indicators for Flume agents on all hosts, including hosts, which are memberships of _group1_ and _group2_ (but configs were changed only for Flume agent in _Flume Default_ group). -- This message was sent by Atlassian JIRA (v6.3.4#6332)